From owner-ietf-fax@mail.imc.org  Wed Aug  1 08:32:59 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA29545
	for <fax-archive@odin.ietf.org>; Wed, 1 Aug 2001 08:32:58 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f71BrtF25706
	for ietf-fax-bks; Wed, 1 Aug 2001 04:53:55 -0700 (PDT)
Received: from bulls.mei.co.jp (bulls.mei.co.jp [202.224.189.25])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f71Brqs25700
	for <ietf-fax@imc.org>; Wed, 1 Aug 2001 04:53:53 -0700 (PDT)
Received: by bulls.mei.co.jp (8.11.4/3.7W) with ESMTP id f71BrXB08805
	for <ietf-fax@imc.org>; Wed, 1 Aug 2001 20:53:33 +0900 (JST)
Received: by dodgers.mei.co.jp (8.9.1/3.7W) with SMTP id UAA11894
	for <ietf-fax@imc.org>; Wed, 1 Aug 2001 20:53:31 +0900 (JST)
Received: from [133.185.137.6] by m-bb.mgcs.mei.co.jp
          via smtpd (for [157.8.1.150]) with SMTP; 1 Aug 2001 11:53:33 UT
Received: from mlsv1.mgcs.mei.co.jp
	by mlsv0.mgcs.mei.co.jp (8.9.3/3.7W-HUB) with ESMTP id UAA19057
	for <ietf-fax@imc.org>; Wed, 1 Aug 2001 20:53:32 +0900 (JST)
Received: from mlsv2.rdmg.mgcs.mei.co.jp
	by mlsv1.mgcs.mei.co.jp (8.9.3/3.7W-MGCS) with ESMTP id UAA11975
	for <ietf-fax@imc.org>; Wed, 1 Aug 2001 20:53:31 +0900 (JST)
Received: from d23n59.rdmg.mgcs.mei.co.jp
	by mlsv2.rdmg.mgcs.mei.co.jp (8.9.3/3.7W-RDMG) with SMTP id UAA02697
	for <ietf-fax@imc.org>; Wed, 1 Aug 2001 20:53:31 +0900 (JST)
Message-Id: <200108011155.AA00043@d23n59.rdmg.mgcs.mei.co.jp>
From: "Toyoda, Kiyoshi" <ktoyoda@rdmg.mgcs.mei.co.jp>
Date: Wed, 01 Aug 2001 20:55:33 +0900
To: ietf-fax@imc.org
Subject: Reivised  Service I-D responding to "Request for IESG Consideration on Service I-D"
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.12
Content-Type: multipart/mixed;
	boundary="--------------------3267630400572435"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


This is multipart message.

----------------------3267630400572435
Content-Type: text/plain; charset=us-ascii

Folks,

I revised Service I-D attached. The revised points are below
"ned.freed@mrochek.com wrote:".  Please comment.

ned.freed@mrochek.com wrote:
>
>> A Simple Mode of Facsimile Using Internet Mail
>>   draft-ietf-fax-service-v2-03.txt
>
>> Status: Draft Standard
>
>A few things need to be fixed before this one will be ready for IETF
>last call.
>
>(1) This document apparently obsoletes RFC 2305 but never mentions RFC 2305.
>    At a minimum you need to have "Obsoletes: RFC 2305" in the document header,
>    you need to include RFC 2305 in the references, and you need to have a
>    section explaining the differences between this document and RFC 2305.

Revised draft mentions RFC2305 in SUMMARY and has APPENDIX B which explains 
the differences between this document and RFC 2305.


>
>(2) I don't insist on it, but since this document talks about "network
>    printers" some discussion of its relationship with IPP might be
>    appropriate.

I didn't revise the draft regarding this point.
If anybody has any idea, please comment it.

>
>(3) References [10] and [11] needs to be updated to refer to the recently
>    approved updates to RFC 2303 and RFC 2304. (It is OK to reference a
>    draft that is in the RFC publication queue, as these are.)

Revised draft refer to below
"draft-ietf-fax-faxaddr-v2-04.txt"
"draft-ietf-fax-minaddr-v2-04.txt"

>
>(4) This document has lots of references, some of which are normative and
>    some of which are not. (And yes, I'm well aware of the issue surrounding
>    the updates to the DSN specifications.) It would be really helpful if
>    you could separate the normative and non-normative references, making
>    it clear what needs to in place before this can actually be published.

I separate REFERENCES to the normative and non-normative. 


>
>(5) Appendix A uses the capitalized phrase "NOT REQUIRED". We try and reserve
>    use of capitalization of this sort to the terms defined in RFC 2119.
>    (And yes, I do realize that this wasn't caught in the previous version.)
>    I suggest that you either lower case these words or reword to use the
>    regular capitalized terms (MAY is the one that comes to mind).


"NOT REQUIRED" to "not required"



Kiyoshi Toyoda

----------------------3267630400572435
Content-Type: application/octet-stream;
	name="draft-ietf-fax-service-v2-04.txt"
Content-Disposition: attachment;
	filename="draft-ietf-fax-service-v2-04.txt"
Content-Transfer-Encoding: base64

DQoNCg0KDQoNCg0KTmV0d29yayBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICBLLiBUb3lvZGENCkludGVybmV0IERyYWZ0ICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBILiBPaG5vDQpKdWx5
IDI3LCAyMDAxICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICBKLiBNdXJhaQ0KRXhwaXJlcyBKYW51YXJ5IDIwMDIgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICBXSURFIFByb2plY3QNCk9ic29sZXRlczogUkZDMjMwNSAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBELiBXaW5nDQpk
cmFmdC1pZXRmLWZheC1zZXJ2aWNlLXYyLTA0LnR4dCAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBDaXNjbw0KDQoNCg0KICAgICAgICAgICAgIEEgU2ltcGxlIE1vZGUgb2Yg
RmFjc2ltaWxlIFVzaW5nIEludGVybmV0IE1haWwNCg0KU3RhdHVzIG9mIHRoaXMgTWVtbw0K
DQogICBUaGlzIGRvY3VtZW50IGlzIGFuIEludGVybmV0LURyYWZ0IGFuZCBpcyBpbiBmdWxs
IGNvbmZvcm1hbmNlDQogICB3aXRoIGFsbCBwcm92aXNpb25zIG9mIFNlY3Rpb24gMTAgb2Yg
UkZDMjAyNi4gSW50ZXJuZXQtRHJhZnRzIGFyZQ0KICAgd29ya2luZyBkb2N1bWVudHMgb2Yg
dGhlIEludGVybmV0IEVuZ2luZWVyaW5nIFRhc2sgRm9yY2UgKElFVEYpLCANCiAgIGl0cyBh
cmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5vdGUgdGhhdCBvdGhlciBncm91cHMg
bWF5IGFsc28NCiAgIGRpc3RyaWJ1dGUgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQt
RHJhZnRzLg0KDQogICBJbnRlcm5ldC1EcmFmdHMgYXJlIGRyYWZ0IGRvY3VtZW50cyB2YWxp
ZCBmb3IgYSBtYXhpbXVtIG9mIHNpeCBtb250aHMNCiAgIGFuZCBtYXkgYmUgdXBkYXRlZCwg
cmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMgYXQgYW55DQogICB0
aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJhZnRzIGFzIHJl
ZmVyZW5jZQ0KICAgbWF0ZXJpYWwgb3IgdG8gY2l0ZSB0aGVtIG90aGVyIHRoYW4gYXMgIndv
cmsgaW4gcHJvZ3Jlc3MuIg0KDQogICBUbyB2aWV3IHRoZSBlbnRpcmUgbGlzdCBvZiBjdXJy
ZW50IEludGVybmV0LURyYWZ0cywgcGxlYXNlIGNoZWNrDQogICB0aGUgIjFpZC1hYnN0cmFj
dHMudHh0IiBsaXN0aW5nIGNvbnRhaW5lZCBpbiB0aGUgSW50ZXJuZXQtRHJhZnRzDQogICBT
aGFkb3cgRGlyZWN0b3JpZXMgb24gZnRwLmlzLmNvLnphIChBZnJpY2EpLCBmdHAubm9yZHUu
bmV0DQogICAoTm9ydGhlcm4gRXVyb3BlKSwgZnRwLm5pcy5nYXJyLml0IChTb3V0aGVybiBF
dXJvcGUpLCBtdW5uYXJpLm96LmF1DQogICAoUGFjaWZpYyBSaW0pLCBmdHAuaWV0Zi5vcmcg
KFVTIEVhc3QgQ29hc3QpLCBvciBmdHAuaXNpLmVkdQ0KICAgKFVTIFdlc3QgQ29hc3QpLg0K
DQogICBUaGlzIGRyYWZ0IGlzIGEgcHJvZHVjdCBvZiB0aGUgSUVURiBJbnRlcm5ldCBGYXgg
d29ya2luZyBncm91cC4gIFRvDQogICBzdWJzY3JpYmUgdG8gdGhlIG1haWxpbmcgbGlzdCwg
c2VuZCBhIG1lc3NhZ2UgdG8NCiAgIGlldGYtZmF4LXJlcXVlc3RAaW1jLm9yZyB3aXRoIHRo
ZSBsaW5lICJzdWJzY3JpYmUiIGluIHRoZSBib2R5IG9mIHRoZQ0KICAgbWVzc2FnZS4gIEFy
Y2hpdmVzIGFyZSBhdmFpbGFibGUgZnJvbSA8aHR0cDovL3d3dy5pbWMub3JnL2lldGYtZmF4
Pi4NCg0KQ29weXJpZ2h0IE5vdGljZQ0KDQogICBDb3B5cmlnaHQgKEMpIFRoZSBJbnRlcm5l
dCBTb2NpZXR5ICgxOTk5LDIwMDApLiAgQWxsIFJpZ2h0cyBSZXNlcnZlZC4NCg0KU1VNTUFS
WQ0KDQogICBUaGlzIGRvY3VtZW50IGlzIGEgcmV2aXNlZCB2ZXJzaW9uIG9mIFJGQyAyMzA1
Lg0KICAgVGhlIHJldmlzaW9ucywgc3VtbWFyaXplZCBpbiB0aGUgbGlzdCBhdHRhY2hlZCBh
cyBBcHBlbmRpeCBCIHRvIHRoaXMgDQogICBkb2N1bWVudCwgYXJlIGJhc2VkIG9uIHRoZSBz
dWdnZXN0aW9ucyBmb3IgaW1wcm92ZW1lbnRzIHRoYXQgaGF2ZSBiZWVuIA0KICAgbWFkZSBz
aW5jZSBSRkMgMjMwNSB3YXMgaXNzdWVkIGluIE1hcmNoIDE5OTguIFRoZXJlIGFyZSBubyB0
ZWNobmljYWwNCiAgIGNoYW5nZXMgZnJvbSBSRkMyMzA1Lg0KIA0KDQoNClRveW9kYSwgZXQu
IGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDIwMDIgICAgICAgICAgICAgICAgICAg
W1BhZ2UgMV0NCgwNCkludGVybmV0IERyYWZ0ICAgICAgICAgIFNpbXBsZSBNb2RlIG9mIEZh
Y3NpbWlsZSAgICAgICAgICAgICAgIEp1bHkgMjAwMQ0KDQoNCiAgIFRoaXMgc3BlY2lmaWNh
dGlvbiBwcm92aWRlcyBmb3IgInNpbXBsZSBtb2RlIiBjYXJyaWFnZSBvZiBmYWNzaW1pbGUN
CiAgIGRhdGEgdXNpbmcgSW50ZXJuZXQgbWFpbC4gIEV4dGVuc2lvbnMgdG8gdGhpcyBkb2N1
bWVudCB3aWxsIGZvbGxvdy4NCiAgIFRoZSBjdXJyZW50IHNwZWNpZmljYXRpb24gZW1wbG95
cyBzdGFuZGFyZCBwcm90b2NvbHMgYW5kIGZpbGUgZm9ybWF0cw0KICAgc3VjaCBhcyBUQ1Av
SVAsIEludGVybmV0IG1haWwgcHJvdG9jb2xzIFsxLCAyLCAzXSwgTUlNRSBbNCwgMTAsIDEx
XSwNCiAgIGFuZCBUSUZGIGZvciBGYWNzaW1pbGUgWzUsIDEyLCAxNF0uICBJdCBjYW4gc2Vu
ZCBpbWFnZXMgbm90IG9ubHkgdG8NCg0KICAgb3RoZXIgSW50ZXJuZXQtYXdhcmUgZmFjc2lt
aWxlIGRldmljZXMgYnV0IGFsc28gdG8gSW50ZXJuZXQtbmF0aXZlDQogICBzeXN0ZW1zLCBz
dWNoIGFzIFBDcyB3aXRoIGNvbW1vbiBlbWFpbCByZWFkZXJzIHdoaWNoIGNhbiBoYW5kbGUg
TUlNRQ0KICAgbWFpbCBhbmQgVElGRiBmb3IgRmFjc2ltaWxlIGRhdGEuICBUaGUgc3BlY2lm
aWNhdGlvbiBmYWNpbGl0YXRlcw0KICAgY29tbXVuaWNhdGlvbiBhbW9uZyBleGlzdGluZyBm
YWNzaW1pbGUgZGV2aWNlcywgSW50ZXJuZXQgbWFpbCBhZ2VudHMsDQogICBhbmQgdGhlIGdh
dGV3YXlzIHdoaWNoIGNvbm5lY3QgdGhlbS4NCg0KICAgVGhlIElFVEYgaGFzIGJlZW4gbm90
aWZpZWQgb2YgaW50ZWxsZWN0dWFsIHByb3BlcnR5IHJpZ2h0cyBjbGFpbWVkIGluDQogICBy
ZWdhcmQgdG8gc29tZSBvciBhbGwgb2YgdGhlIHNwZWNpZmljYXRpb24gY29udGFpbmVkIGlu
IHRoaXMNCiAgIGRvY3VtZW50LiAgRm9yIG1vcmUgaW5mb3JtYXRpb24gY29uc3VsdCB0aGUg
b25saW5lIGxpc3Qgb2YgY2xhaW1lZA0KICAgcmlnaHRzIGluIDxodHRwOi8vd3d3LmlldGYu
b3JnL2lwci5odG1sPi4NCg0KICAgVGhlIGtleSB3b3JkcyAiTVVTVCIsICJNVVNUIE5PVCIs
ICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLA0KICAgIlNIT1VMRCIsICJTSE9V
TEQgTk9UIiwgIlJFQ09NTUVOREVEIiwgICJNQVkiLCBhbmQgIk9QVElPTkFMIiBpbiB0aGlz
DQogICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQgYXMgZGVzY3JpYmVkIGluIFsx
M10uDQoNCjEgIFNDT1BFDQoNCiAgIFRoaXMgc3BlY2lmaWNhdGlvbiBkZWZpbmVzIG1lc3Nh
Z2UtYmFzZWQgZmFjc2ltaWxlIGNvbW11bmljYXRpb24NCiAgIG92ZXIgdGhlIEludGVybmV0
LiAgSXQgZGVzY3JpYmVzIGEgbWluaW11bSBzZXQgb2YgY2FwYWJpbGl0aWVzLA0KICAgdGFr
aW5nIGludG8gYWNjb3VudCB0aG9zZSBvZiB0eXBpY2FsIGZhY3NpbWlsZSBkZXZpY2VzIGFu
ZCBQQ3MgdGhhdA0KICAgY2FuIGdlbmVyYXRlIGZhY3NpbWlsZSBkYXRhLg0KDQogICBBIEcz
RmF4IGRldmljZSBoYXMgc3Vic3RhbnRpYWwgcmVzdHJpY3Rpb25zIGR1ZSB0byBzcGVjaWZp
Y2F0aW9ucyBpbg0KICAgdGhlIHN0YW5kYXJkcywgc3VjaCBhcyBmb3IgdGltZXJzLiBUaGlz
IHNwZWNpZmljYXRpb24gZGVmaW5lcyBhDQogICBwcm9maWxlIGZvciBJbnRlcm5ldCBtYWls
LCByYXRoZXIgdGhhbiBjcmVhdGluZyBhIGRpc3RpbmN0ICJmYWNzaW1pbGUNCiAgIG92ZXIg
dGhlIEludGVybmV0IiBzZXJ2aWNlLiAgVGhlIHNlbWFudGljcyByZXN1bHRpbmcgZnJvbSB0
aGUgcHJvZmlsZQ0KICAgYXJlIGRlc2lnbmVkIHRvIGJlIGNvbXBhdGlibGUgd2l0aCBmYWNz
aW1pbGUgb3BlcmF0aW9uIG92ZXIgdGhlDQogICBnZW5lcmFsIHN3aXRjaGVkIHRlbGVwaG9u
ZSBuZXR3b3JrLCBzbyB0aGF0IGdhdGV3YXlzIGJldHdlZW4NCiAgIGZhY3NpbWlsZSBhbmQg
SW50ZXJuZXQgbWFpbCBjYW4gb3BlcmF0ZSB3aXRoIHZlcnkgaGlnaCBmaWRlbGl0eS4NCg0K
ICAgVGhlIHJlYXNvbiBmb3IgZGV2ZWxvcGluZyB0aGlzIGNhcGFiaWxpdHkgYXMgYW4gZW1h
aWwgcHJvZmlsZSBpcyB0bw0KICAgcGVybWl0IGludGVyd29ya2luZyBhbW9uZ3N0IGZhY3Np
bWlsZSBhbmQgZW1haWwgdXNlcnMuICBGb3IgZXhhbXBsZQ0KICAgaXQgaXMgaW50ZW5kZWQg
dGhhdCBleGlzdGluZyBlbWFpbCB1c2VycyBiZSBhYmxlIHRvIHNlbmQgbm9ybWFsDQogICBt
ZXNzYWdlcyB0byBsaXN0cyBvZiB1c2VycywgaW5jbHVkaW5nIGZhY3NpbWlsZS1iYXNlZCBy
ZWNpcGllbnRzLCBhbmQNCiAgIHRoYXQgb3RoZXIgZW1haWwgcmVjaXBpZW50cyBzaGFsbCBi
ZSBhYmxlIHRvIHJlcGx5IHRvIHRoZSBvcmlnaW5hbA0KICAgYW5kIGNvbnRpbnVlIHRvIGlu
Y2x1ZGUgZmFjc2ltaWxlIHJlY2lwaWVudHMuICBTaW1pbGFybHkgaXQgaXMNCiAgIGludGVu
ZGVkIHRoYXQgZXhpc3RpbmcgZW1haWwgc29mdHdhcmUgd29yayB3aXRob3V0IG1vZGlmaWNh
dGlvbiBhbmQNCiAgIG5vdCBiZSByZXF1aXJlZCB0byBwcm9jZXNzIG5ldywgb3IgZGlmZmVy
ZW50IGRhdGEgc3RydWN0dXJlcywgYmV5b25kDQogICB3aGF0IGlzIG5vcm1hbCBmb3IgSW50
ZXJuZXQgbWFpbCB1c2Vycy4gIEV4aXN0aW5nIGVtYWlsIHNlcnZpY2UNCiAgIHN0YW5kYXJk
cyBhcmUgdXNlZCwgcmF0aGVyIHRoYW4gcmVwbGljYXRpbmcgbWVjaGFuaXNtcyB3aGljaCBh
cmUgbW9yZQ0KICAgdGFpbG9yZWQgdG8gZXhpc3RpbmcgZmFjc2ltaWxlIHN0YW5kYXJkcywg
dG8gZW5zdXJlIHRoaXMNCiAgIGNvbXBhdGliaWxpdHkgd2l0aCBleGlzdGluZyBlbWFpbCBz
ZXJ2aWNlLg0KDQoNCg0KVG95b2RhLCBldC4gYWwuICAgICAgICAgICBFeHBpcmVzIEphbnVh
cnkgMjAwMiAgICAgICAgICAgICAgICAgICBbUGFnZSAyXQ0KDA0KSW50ZXJuZXQgRHJhZnQg
ICAgICAgICAgU2ltcGxlIE1vZGUgb2YgRmFjc2ltaWxlICAgICAgICAgICAgICAgSnVseSAy
MDAxDQoNCg0KMS4xIFNlcnZpY2VzDQogICBBIGZhY3NpbWlsZS1jYXBhYmxlIGRldmljZSB0
aGF0IHVzZXMgVC40IFsxNV0gYW5kIHRoZSBnZW5lcmFsIHN3aXRjaGVkDQogICB0ZWxlcGhv
bmUgbmV0d29yayAoR1NUTikgaXMgY2FsbGVkIGEgIkczRmF4IGRldmljZSIgaW4gdGhpcw0K
ICAgc3BlY2lmaWNhdGlvbi4gIEFuICJJRmF4IGRldmljZSIgaXMgYW4gSW50ZXJuZXQtIGFj
Y2Vzc2libGUgZGV2aWNlDQogICBjYXBhYmxlIG9mIHNlbmRpbmcsIHJlY2VpdmluZyBvciBm
b3J3YXJkaW5nIEludGVybmV0IGZheGVzLiAgQQ0KICAgbWVzc2FnZSBjYW4gYmUgc2VudCB0
byBhbiBJRmF4IGRldmljZSB1c2luZyAgYW4gSW50ZXJuZXQgbWFpbA0KICAgYWRkcmVzcy4g
QSBtZXNzYWdlIGNhbiBiZSBzZW50IHRvIGEgRzNGYXggZGV2aWNlICB1c2luZyBhbiBJbnRl
cm5ldA0KICAgbWFpbCBhZGRyZXNzOyB0aGUgbWVzc2FnZSBNQVkgYmUgZm9yd2FyZGVkIHZp
YSBhbiBJRmF4IG9mZnJhbXANCiAgIGdhdGV3YXkuDQoNCjEuMiBDYXNlcw0KDQogICBUaGlz
IHNwZWNpZmljYXRpb24gcHJvdmlkZXMgZm9yIGNvbW11bmljYXRpb24gYmV0d2VlbiBlYWNo
IG9mIHRoZQ0KICAgZm9sbG93aW5nIGNvbWJpbmF0aW9uczoNCiAgIEludGVybmV0IG1haWwg
ICAgICAgICAgICAgPT4gIE5ldHdvcmsgcHJpbnRlcg0KICAgSW50ZXJuZXQgbWFpbCAgICAg
ICAgICAgICA9PiAgT2ZmcmFtcCBnYXRld2F5IChmb3J3YXJkIHRvDQogICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICBHM0ZheCkNCiAgIE5ldHdvcmsgc2Nhbm5lciAgICAgICAg
ICAgPT4gIE5ldHdvcmsgcHJpbnRlcg0KICAgTmV0d29yayBzY2FubmVyICAgICAgICAgICA9
PiAgT2ZmcmFtcCBnYXRld2F5IChmb3J3YXJkIHRvDQogICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICBHM0ZheCkNCiAgIE5ldHdvcmsgc2Nhbm5lciAgICAgICAgICAgPT4gIElu
dGVybmV0IG1haWwNCg0KDQoyICBDT01NVU5JQ0FUSU9OIFBST1RPQ09MUw0KDQogICBUaGUg
c2V0IG9mIGNvbnZlbnRpb25zIG5lY2Vzc2FyeSB0byBhY2hpZXZlIGZhY3NpbWlsZS0gY29t
cGF0aWJsZQ0KICAgc2VydmljZSBjb3ZlcnMgYmFzaWMgZGF0YSB0cmFuc3BvcnQsIGRvY3Vt
ZW50IGRhdGEgZm9ybWF0cywgbWVzc2FnZQ0KICAgKGRvY3VtZW50KSBhZGRyZXNzaW5nLCBk
ZWxpdmVyeSBjb25maXJtYXRpb24sIGFuZCBtZXNzYWdlIHNlY3VyaXR5Lg0KICAgSW4gdGhp
cyBzZWN0aW9uLCB0aGUgZmlyc3QgNCBhcmUgY292ZXJlZC4gIFRoZSByZW1haW5kZXIgYXJl
IGNvdmVyZWQNCiAgIGluIGZvbGxvd2luZyBzZWN0aW9ucywgYWxvbmcgd2l0aCBhZGRpdGlv
bmFsIGRldGFpbHMgZm9yIGFkZHJlc3NpbmcNCiAgIGFuZCBmb3JtYXRzLg0KDQoyLjEgVHJh
bnNwb3J0DQoNCiAgIFRoaXMgc2VjdGlvbiBkZXNjcmliZXMgbWVjaGFuaXNtcyBpbnZvbHZl
ZCBpbiB0aGUgdHJhbnNwb3J0IGJldHdlZW4NCiAgIElGQVggZGV2aWNlcy4NCg0KMi4xLjEg
ICAgIFJlbGF5DQoNCiAgIERhdGEgdHJhbnNmZXIgTUFZIGJlIGFjaGlldmVkIHVzaW5nIHN0
YW5kYXJkIEludGVybmV0IG1haWwgdHJhbnNmZXINCiAgIG1lY2hhbmlzbXNbMSwgM10uICBU
aGUgZm9ybWF0IG9mIGFkZHJlc3NlcyBNVVNUIGNvbmZvcm0gdG8gdGhlIFJGQw0KICAgODIx
IDxhZGRyLXNwZWM+IGFuZCBSRkMgODIyIDxtYWlsYm94PiBJbnRlcm5ldCBtYWlsIHN0YW5k
YXJkcyBbMSwgMiwNCiAgIDNdLg0KDQoyLjEuMiAgICAgR2F0ZXdheQ0KDQogICBBIGdhdGV3
YXkgdHJhbnNsYXRlcyBiZXR3ZWVuIGRpc3NpbWlsYXIgZW52aXJvbm1lbnRzLiAgRm9yIElG
YXgsIGENCiAgIGdhdGV3YXkgY29ubmVjdHMgYmV0d2VlbiBJbnRlcm5ldCBtYWlsIGFuZCB0
aGUgVC40L0dTVE4gZmFjc2ltaWxlLg0KICAgR2F0ZXdheXMgY2FuIHNlcnZpY2UgbXVsdGlw
bGUgVC40L0dTVE4gZmFjc2ltaWxlIHVzZXJzIG9yIGNhbiBzZXJ2aWNlDQogICBvbmx5IG9u
ZS4gIEluIHRoZSBmb3JtZXIgY2FzZSwgdGhleSBzZXJ2ZSBhcyBhIGNsYXNzaWMgIm1haWwg
dHJhbnNmZXINCiAgIGFnZW50IiAoTVRBKSBhbmQgaW4gdGhlIGxhdHRlciBhcyBhIGNsYXNz
aWMgIm1haWwgdXNlciBhZ2VudCIgKFVBKS4NCg0KVG95b2RhLCBldC4gYWwuICAgICAgICAg
ICBFeHBpcmVzIEphbnVhcnkgMjAwMiAgICAgICAgICAgICAgICAgICBbUGFnZSAzXQ0KDA0K
SW50ZXJuZXQgRHJhZnQgICAgICAgICAgU2ltcGxlIE1vZGUgb2YgRmFjc2ltaWxlICAgICAg
ICAgICAgICAgSnVseSAyMDAxDQoNCg0KDQogICBBbiBvbnJhbXAgaXMgYSBnYXRld2F5IHdo
aWNoIGNvbm5lY3RzIGZyb20gVC40L0dTVE4gZmFjc2ltaWxlIHRvDQogICBJbnRlcm5ldCBt
YWlsLiAgQW4gb2ZmcmFtcCBpcyBhIGdhdGV3YXkgd2hpY2ggY29ubmVjdHMgZnJvbSBJbnRl
cm5ldA0KICAgbWFpbCB0byBULjQvR1NUTiBmYWNzaW1pbGUuIEJlaGF2aW9yIG9mIG9ucmFt
cHMgaXMgb3V0IG9mIHNjb3BlIGZvcg0KICAgdGhpcyBzcGVjaWZpY2F0aW9uLg0KDQogICBU
aGlzIHNwZWNpZmljYXRpb24gZGVzY3JpYmVzIHRoZSBJbnRlcm5ldCBtYWlsIHNlcnZpY2Ug
cG9ydGlvbiBvZg0KICAgb2ZmcmFtcCBhZGRyZXNzaW5nLCBjb25maXJtYXRpb24gYW5kIGZh
aWx1cmUgbm90aWZpY2F0aW9uLiAgRGV0YWlscw0KICAgYXJlIHByb3ZpZGVkIGluIGxhdGVy
IHNlY3Rpb25zLg0KDQoyLjEuMyAgICAgTWFpbGJveCBwcm90b2NvbHMNCg0KICAgQW4gb2Zm
cmFtcCBnYXRld2F5IHRoYXQgb3BlcmF0ZSBhcyBhbiBNVEEgc2VydmluZyBtdWx0aXBsZSB1
c2Vycw0KICAgU0hPVUxEIHVzZSBTTVRQOyBhIGdhdGV3YXkgdGhhdCBvcGVyYXRlcyBhcyBh
IFVBIHNlcnZpbmcgYSBzaW5nbGUNCiAgIG1haWwgcmVjaXBpZW50IE1BWSB1c2UgYSBtYWls
Ym94IGFjY2VzcyBwcm90b2NvbCBzdWNoIGFzIFBPUCBbNl0gb3IgDQogICBzaW1pbGFyIG1h
aWxib3ggYWNjZXNzIHByb3RvY29scy4NCg0KICAgTk9URTogQW4gb2ZmcmFtcCBnYXRld2F5
IHRoYXQgcmVsYXlzIG1haWwgYmFzZWQgb24gYWRkcmVzc2luZw0KICAgaW5mb3JtYXRpb24g
bmVlZHMgdG8gZW5zdXJlIHRoYXQgaXQgdXNlcyBhZGRyZXNzZXMgc3VwcGxpZWQgaW4gdGhl
DQogICBNVEEgZW52ZWxvcGUsIHJhdGhlciB0aGFuIGZyb20gZWxzZXdoZXJlLCBzdWNoIGFz
IGFkZHJlc3NlcyBsaXN0ZWQgaW4NCiAgIHRoZSBtZXNzYWdlIGNvbnRlbnQgaGVhZGVycy4N
Cg0KMi4yIEZvcm1hdHMNCg0KMi4yLjEgICAgIEhlYWRlcnMNCg0KICAgSUZheCBkZXZpY2Vz
IE1VU1QgYmUgY29tcGxpYW50IHdpdGggUkZDIDgyMiBhbmQgUkZDMTEyMywgd2hpY2ggZGVm
aW5lDQogICB0aGUgZm9ybWF0IG9mIG1haWwgaGVhZGVycy4gIFRoZSBoZWFkZXIgb2YgYW4g
SUZheCBtZXNzYWdlIFNIT1VMRA0KICAgaW5jbHVkZSBNZXNzYWdlLUlEIGFuZCBNVVNUIGlu
Y2x1ZGUgYWxsIGZpZWxkcyByZXF1aXJlZCBieSBbMiwgM10sDQogICBzdWNoIGFzIERBVEUg
YW5kIEZST00uDQoNCjIuMi4yICAgICBNSU1FDQoNCiAgIElGYXggZGV2aWNlcyBNVVNUIGJl
IGNvbXBsaWFudCB3aXRoIE1JTUUgWzRdLCBleGNlcHQgYXMgbm90ZWQgaW4NCiAgIEFwcGVu
ZGl4IEEuDQoNCjIuMi4zICAgICBDb250ZW50DQoNCiAgIFRoZSBkYXRhIGZvcm1hdCBvZiB0
aGUgZmFjc2ltaWxlIGltYWdlIGlzIGJhc2VkIG9uIHRoZSBtaW5pbXVtIHNldCBvZg0KICAg
VElGRiBmb3IgRmFjc2ltaWxlIFs1XSwgYWxzbyBrbm93biBhcyB0aGUgUyBwcm9maWxlLiAg
IFN1Y2ggZmFjc2ltaWxlDQogICBkYXRhIGFyZSBpbmNsdWRlZCBpbiBhIE1JTUUgb2JqZWN0
IGJ5IHVzZSBvZiB0aGUgaW1hZ2UvVElGRiBzdWItdHlwZQ0KICAgWzEyXS4gIEFkZGl0aW9u
YWwgcnVsZXMgZm9yIHRoZSB1c2Ugb2YgVElGRiBmb3IgRmFjc2ltaWxlLCBmb3IgdGhlDQog
ICBtZXNzYWdlLWJhc2VkIEludGVybmV0IGZhY3NpbWlsZSBhcHBsaWNhdGlvbiwgYXJlIGRl
ZmluZWQgbGF0ZXIuDQoNCjIuMi40ICAgICBNdWx0aXBhcnQNCg0KICAgQSBzaW5nbGUgbXVs
dGktcGFnZSBkb2N1bWVudCBTSE9VTEQgYmUgc2VudCBhcyBhIHNpbmdsZSBtdWx0aS0gcGFn
ZQ0KICAgVElGRiBmaWxlLCBldmVuIHRob3VnaCByZWNpcGllbnRzIE1VU1QgcHJvY2VzcyBt
dWx0aXBhcnQvbWl4ZWQNCiAgIGNvbnRhaW5pbmcgbXVsdGlwbGUgVElGRiBmaWxlcy4gSWYg
bXVsdGlwYXJ0IGNvbnRlbnQgaXMgcHJlc2VudCBhbmQNCiAgIHByb2Nlc3Npbmcgb2YgYW55
IHBhcnQgZmFpbHMsIHRoZW4gcHJvY2Vzc2luZyBmb3IgdGhlIGVudGlyZSBtZXNzYWdlDQog
ICBpcyB0cmVhdGVkIGFzIGZhaWxpbmcsIHBlciBbUHJvY2Vzc2luZyBmYWlsdXJlXSBiZWxv
dy4NCg0KDQpUb3lvZGEsIGV0LiBhbC4gICAgICAgICAgIEV4cGlyZXMgSmFudWFyeSAyMDAy
ICAgICAgICAgICAgICAgICAgIFtQYWdlIDRdDQoMDQpJbnRlcm5ldCBEcmFmdCAgICAgICAg
ICBTaW1wbGUgTW9kZSBvZiBGYWNzaW1pbGUgICAgICAgICAgICAgICBKdWx5IDIwMDENCg0K
DQoNCjIuMyBFcnJvciBIYW5kbGluZw0KDQoyLjMuMSAgICAgRGVsaXZlcnkgZmFpbHVyZQ0K
DQogICBUaGlzIHNlY3Rpb24gZGVzY3JpYmVzIGV4aXN0aW5nIHJlcXVpcmVtZW50cyBmb3Ig
SW50ZXJuZXQgbWFpbCwNCiAgIHJhdGhlciB0aGFuIGluZGljYXRpbmcgc3BlY2lhbCByZXF1
aXJlbWVudHMgZm9yIElGYXggZGV2aWNlcy4NCg0KICAgSW4gdGhlIGV2ZW50IG9mIHJlbGF5
IGZhaWx1cmUsIHRoZSBzZW5kaW5nIHJlbGF5IE1VU1QgZ2VuZXJhdGUgYQ0KICAgZmFpbHVy
ZSBtZXNzYWdlLCB3aGljaCBTSE9VTEQgYmUgaW4gdGhlIGZvcm1hdCBvZiBhIERTTi4gWzld
DQoNCiAgICAgICAgTk9URTogIEludGVybmV0IG1haWwgdHJhbnNwb3J0ZWQgdmlhIFNNVFAg
TVVTVCBjb250YWluIGEgTUFJTA0KICAgICAgICBGUk9NIGFkZHJlc3MgYXBwcm9wcmlhdGUg
Zm9yIGRlbGl2ZXJ5IG9mIHJldHVybiBub3RpY2VzIFtBbHNvDQogICAgICAgIHNlZSBzZWN0
aW9uIDUuMi42XQ0KDQoyLjMuMiAgICAgUHJvY2Vzc2luZyBmYWlsdXJlDQoNCiAgIElGYXgg
ZGV2aWNlcyB3aXRoIGxpbWl0ZWQgY2FwYWJpbGl0aWVzIG1pZ2h0IGJlIHVuYWJsZSB0byBw
cm9jZXNzIHRoZQ0KICAgY29udGVudCBvZiBhIG1lc3NhZ2UuICBJZiB0aGlzIG9jY3VycyBp
dCBpcyBpbXBvcnRhbnQgdG8gZW5zdXJlIHRoYXQNCiAgIHRoZSBtZXNzYWdlIGlzIG5vdCBs
b3N0IHdpdGhvdXQgYW55IG5vdGljZS4gTm90aWNlIE1BWSBiZSBwcm92aWRlZCBpbg0KICAg
YW55IGFwcHJvcHJpYXRlIGZhc2hpb24sIGFuZCB0aGUgZXhhY3QgaGFuZGxpbmcgaXMgYSBs
b2NhbCBtYXR0ZXIuDQogICAoQWxzbyBzZWUgQXBwZW5kaXggQSwgc2Vjb25kIGJ1bGxldC4p
DQoNCjMgIEFERFJFU1NJTkcNCg0KMy4xIENsYXNzaWMgRW1haWwgRGVzdGluYXRpb25zDQoN
CiAgIE1lc3NhZ2VzIGJlaW5nIHNlbnQgdG8gbm9ybWFsIEludGVybmV0IG1haWwgcmVjaXBp
ZW50cyB3aWxsIHVzZQ0KICAgc3RhbmRhcmQgSW50ZXJuZXQgbWFpbCBhZGRyZXNzZXMsIHdp
dGhvdXQgYWRkaXRpb25hbCBjb25zdHJhaW50cy4NCg0KMy4yIEczRmF4IERldmljZXMNCg0K
ICAgRzNGYXggZGV2aWNlcyBhcmUgYWNjZXNzZWQgdmlhIGFuIElGQVggb2ZmcmFtcCBnYXRl
d2F5LCB3aGljaA0KICAgcGVyZm9ybXMgYW55IGF1dGhvcml6ZWQgdGVsZXBob25lIGRpYWwt
dXAuDQoNCjMuMyBBZGRyZXNzIEZvcm1hdHMgVXNlZCBieSBPZmZyYW1wcw0KDQogICBXaGVu
IGEgRzNGYXggZGV2aWNlIGlzIGlkZW50aWZpZWQgYnkgYSB0ZWxlcGhvbmUgbnVtYmVyLCB0
aGUgZW50aXJlDQogICBhZGRyZXNzIHVzZWQgZm9yIHRoZSBHM2ZheCBkZXZpY2UsIGluY2x1
ZGluZyB0aGUgbnVtYmVyIGFuZCBvZmZyYW1wDQogICBob3N0IHJlZmVyZW5jZSBNVVNUIGJl
IGNvbnRhaW5lZCB3aXRoaW4gc3RhbmRhcmQgSW50ZXJuZXQgbWFpbA0KICAgdHJhbnNwb3J0
IGZpZWxkcywgc3VjaCBhcyBSQ1BUIFRPIGFuZCBNQUlMIEZST00gWzEsIDNdLiAgVGhlIGFk
ZHJlc3MNCiAgIE1BWSBiZSBjb250YWluZWQgd2l0aGluIG1lc3NhZ2UgY29udGVudCBmaWVs
ZHMsIHN1Y2ggYXMgPGF1dGhlbnRpYz4NCiAgIGFuZCA8ZGVzdGluYXRpb24+IFsyLCAzXSwg
YXMgYXBwcm9wcmlhdGUuDQoNCiAgIEFzIGZvciBhbGwgSW50ZXJuZXQgbWFpbCBhZGRyZXNz
ZXMsIHRoZSBsZWZ0LWhhbmQtc2lkZSAobG9jYWwtIHBhcnQpDQogICBvZiBhbiBhZGRyZXNz
IGlzIG5vdCB0byBiZSBpbnRlcnByZXRlZCBleGNlcHQgYnkgdGhlIE1UQSB0aGF0IGlzDQog
ICBuYW1lZCBvbiB0aGUgcmlnaHQtaGFuZC1zaWRlIChkb21haW4pLg0KDQogICBUaGUgdGVs
ZXBob25lIG51bWJlciBmb3JtYXQgU0hPVUxEIGNvbmZvcm0gdG8gWzcsIDhdLiAgT3RoZXIN
CiAgIGZvcm1hdHMgTVVTVCBiZSBzeW50YWN0aWNhbGx5IGRpc3RpbmN0IGZyb20gWzcsIDhd
Lg0KDQoNClRveW9kYSwgZXQuIGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDIwMDIg
ICAgICAgICAgICAgICAgICAgW1BhZ2UgNV0NCgwNCkludGVybmV0IERyYWZ0ICAgICAgICAg
IFNpbXBsZSBNb2RlIG9mIEZhY3NpbWlsZSAgICAgICAgICAgICAgIEp1bHkgMjAwMQ0KDQoN
Cg0KNCAgSU1BR0UgRklMRSBGT1JNQVQNCg0KICAgU2VuZGluZyBJRmF4IGRldmljZXMgTVVT
VCBiZSBhYmxlIHRvIHdyaXRlIG1pbmltdW0gc2V0IFRJRkYgZmlsZXMsDQogICBwZXIgdGhl
IHJ1bGVzIGZvciBjcmVhdGluZyBtaW5pbXVtIHNldCBUSUZGIGZpbGVzIGRlZmluZWQgaW4g
VElGRiBmb3INCiAgIEZhY3NpbWlsZSAodGhlIFMgcHJvZmlsZSkgWzVdLCB3aGljaCBpcyBh
bHNvIGNvbXBhdGlibGUgd2l0aCB0aGUNCiAgIHNwZWNpZmljYXRpb24gZm9yIHRoZSBtaW5p
bXVtIHN1YnNldCBvZiBUSUZGLUYgaW4gWzE0XS4gIFJlY2VpdmluZw0KICAgSUZheCBkZXZp
Y2VzIE1VU1QgYmUgYWJsZSB0byByZWFkIG1pbmltdW0gc2V0IFRJRkYgZmlsZXMuDQoNCiAg
IEEgc2VuZGVyIFNIT1VMRCBOT1QgdXNlIFRJRkYgZmllbGRzIGFuZCB2YWx1ZXMgYmV5b25k
IHRoZSBtaW5pbXVtDQogICBzdWJzZXQgb2YgVElGRiBmb3IgRmFjc2ltaWxlIHVubGVzcyB0
aGUgc2VuZGVyIGhhcyBwcmlvciBrbm93bGVkZ2Ugb2YNCiAgIG90aGVyIFRJRkYgZmllbGRz
IG9yIHZhbHVlcyBzdXBwb3J0ZWQgYnkgdGhlIHJlY2lwaWVudC4gIFRoZQ0KICAgbWVjaGFu
aXNtIGZvciBkZXRlcm1pbmluZyBjYXBhYmlsaXRpZXMgb2YgcmVjaXBpZW50cyBpcyBiZXlv
bmQgdGhlDQogICBzY29wZSBvZiB0aGlzIGRvY3VtZW50Lg0KDQo1ICBTRUNVUklUWSBDT05T
SURFUkFUSU9OUw0KDQo1LjEgR2VuZXJhbCBEaXJlY3RpdmUNCg0KICAgVGhpcyBzcGVjaWZp
Y2F0aW9uIGlzIGJhc2VkIG9uIHVzZSBvZiBleGlzdGluZyBJbnRlcm5ldCBtYWlsLiAgVG8N
CiAgIG1haW50YWluIGludGVyb3BlcmFiaWxpdHkgd2l0aCBJbnRlcm5ldCBtYWlsLCBhbnkg
c2VjdXJpdHkgdG8gYmUNCiAgIHByb3ZpZGVkIHNob3VsZCBiZSBwYXJ0IG9mIHRoZSBvZiB0
aGUgSW50ZXJuZXQgc2VjdXJpdHkNCiAgIGluZnJhc3RydWN0dXJlLCByYXRoZXIgdGhhbiBh
IG5ldyBtZWNoYW5pc20gb3Igc29tZSBvdGhlciBtZWNoYW5pc20NCiAgIG91dHNpZGUgb2Yg
dGhlIEludGVybmV0IGluZnJhc3RydWN0dXJlLg0KDQo1LjIgVGhyZWF0cyBhbmQgUHJvYmxl
bXMNCg0KICAgQm90aCBJbnRlcm5ldCBtYWlsIGFuZCBHM0ZheCBzdGFuZGFyZHMgYW5kIG9w
ZXJhdGlvbmFsIHNlcnZpY2VzIGhhdmUNCiAgIHRoZWlyIG93biBzZXQgb2YgdGhyZWF0cyBh
bmQgY291bnRlcm1lYXN1cmVzLiAgVGhpcyBzZWN0aW9uIGF0dGVuZHMNCiAgIG9ubHkgdG8g
dGhlIHNldCBvZiBhZGRpdGlvbmFsIHRocmVhdHMgd2hpY2ggZW5zdWUgZnJvbSBpbnRlZ3Jh
dGluZw0KICAgdGhlIHR3byBzZXJ2aWNlcy4gVGhpcyBzZWN0aW9uIHJldmlld3MgcmVsZXZh
bnQgY29uY2VybnMgYWJvdXQNCiAgIEludGVybmV0IG1haWwgZm9yIElGYXggZW52aXJvbm1l
bnRzLCBhcyB3ZWxsIGFzIGNvbnNpZGVyaW5nIHRoZQ0KICAgcG90ZW50aWFsIHByb2JsZW1z
IHdoaWNoIGNhbiByZXN1bHQgb2YgaW50ZWdyYXRpbmcgdGhlIGV4aXN0aW5nIEczRmF4DQog
ICBzZXJ2aWNlIHdpdGggSW50ZXJuZXQgbWFpbC4NCg0KNS4yLjEgICAgIFNwb29mZWQgc2Vu
ZGVyDQoNCiAgIFRoZSBhY3R1YWwgc2VuZGVyIG9mIHRoZSBtZXNzYWdlIG1pZ2h0IG5vdCBi
ZSB0aGUgc2FtZSBhcyB0aGF0DQogICBzcGVjaWZpZWQgaW4gdGhlIFNlbmRlciBvciBGcm9t
IGZpZWxkcyBvZiB0aGUgbWVzc2FnZSBjb250ZW50IGhlYWRlcnMNCiAgIG9yIHRoZSBNQUlM
IEZST00gYWRkcmVzcyBmcm9tIHRoZSBTTVRQIGVudmVsb3BlLg0KDQogICBJbiBhIHRpZ2h0
bHkgY29uc3RyYWluZWQgZW52aXJvbm1lbnQsIHN1ZmZpY2llbnQgcGh5c2ljYWwgYW5kDQog
ICBzb2Z0d2FyZSBjb250cm9scyBtYXkgYmUgYWJsZSB0byBlbnN1cmUgcHJldmVudGlvbiBv
ZiB0aGlzIHByb2JsZW0uDQogICBUaGUgdXN1YWwgc29sdXRpb24gaXMgdGhyb3VnaCBlbmNy
eXB0aW9uLWJhc2VkIGF1dGhlbnRpY2F0aW9uLCBlaXRoZXINCiAgIGZvciB0aGUgY2hhbm5l
bCBvciBhc3NvY2lhdGVkIHdpdGggdGhlIG9iamVjdCwgYXMgZGlzY3Vzc2VkIGJlbG93Lg0K
DQogICBJdCBzaG91bGQgYmUgcmVjb2duaXplZCB0aGF0IFNNVFAgaW1wbGVtZW50YXRpb25z
IGRvIG5vdCBwcm92aWRlDQogICBpbmhlcmVudCBhdXRoZW50aWNhdGlvbiBvZiB0aGUgc2Vu
ZGVycyBvZiBtZXNzYWdlcywgbm9yIGFyZSBzaXRlcw0KICAgdW5kZXIgb2JsaWdhdGlvbiB0
byBwcm92aWRlIHN1Y2ggYXV0aGVudGljYXRpb24uIEVuZC10by1lbmQNCiAgIGFwcHJvYWNo
ZXMgc3VjaCBhcyBTL01JTUUgYW5kIFBHUC9NSU1FIGFyZSBjdXJyZW50bHkgYmVpbmcgZGV2
ZWxvcGVkDQogICB3aXRoaW4gdGhlIElFVEYuIFRoZXNlIHRlY2hub2xvZ2llcyBjYW4gcHJv
dmlkZSBzdWNoIGF1dGhlbnRpY2F0aW9uLg0KDQoNClRveW9kYSwgZXQuIGFsLiAgICAgICAg
ICAgRXhwaXJlcyBKYW51YXJ5IDIwMDIgICAgICAgICAgICAgICAgICAgW1BhZ2UgNl0NCgwN
CkludGVybmV0IERyYWZ0ICAgICAgICAgIFNpbXBsZSBNb2RlIG9mIEZhY3NpbWlsZSAgICAg
ICAgICAgICAgIEp1bHkgMjAwMQ0KDQoNCg0KNS4yLjIgICAgIFJlc291cmNlcyBjb25zdW1l
ZCBieSBkaWFsb3V0DQoNCiAgIEluIGFkZGl0aW9uIHRvIHRoZSByZXNvdXJjZXMgbm9ybWFs
bHkgY29uc3VtZWQgZm9yIGVtYWlsIChDUFUgY3ljbGVzDQogICBhbmQgZGlzayksIG9mZnJh
bXAgZmFjc2ltaWxlIGNhdXNlcyBhbiBvdXRkaWFsIHdoaWNoIG9mdGVuIGltcG9zZXMNCiAg
IHNpZ25pZmljYW50IHJlc291cmNlIGNvbnN1bXB0aW9uLCBzdWNoIGFzIGZpbmFuY2lhbCBj
b3N0LiBUZWNobmlxdWVzDQoNCiAgIGZvciBlc3RhYmxpc2hpbmcgYXV0aG9yaXphdGlvbiBv
ZiB0aGUgc2VuZGVyIGFyZSBlc3NlbnRpYWwgdG8gdGhvc2UNCiAgIG9mZnJhbXAgZmFjc2lt
aWxlIHNlcnZpY2VzIHRoYXQgbmVlZCB0byBtYW5hZ2Ugc3VjaCBjb25zdW1wdGlvbi4NCg0K
ICAgRHVlIHRvIHRoZSBjb25zdW1wdGlvbiBvZiB0aGVzZSByZXNvdXJjZXMgYnkgZGlhbG91
dCwgdW5zb2xpY2l0ZWQNCiAgIGJ1bGsgZW1haWwgd2hpY2ggY2F1c2VzIGFuIG91dGRpYWwg
aXMgdW5kZXNpcmFibGUuDQoNCiAgIE9mZnJhbXAgZ2F0ZXdheXMgU0hPVUxEIHByb3ZpZGUg
dGhlIGFiaWxpdHkgdG8gYXV0aG9yaXplIHNlbmRlcnMgaW4NCiAgIHNvbWUgbWFubmVyIHRv
IHByZXZlbnQgdW5hdXRob3JpemVkIHVzZSBvZiB0aGUgb2ZmcmFtcC4gVGhlcmUgYXJlIG5v
DQogICBzdGFuZGFyZCB0ZWNobmlxdWVzIGZvciBhdXRob3JpemF0aW9uIHVzaW5nIEludGVy
bmV0IHByb3RvY29scy4NCg0KICAgVHlwaWNhbCBzb2x1dGlvbnMgdXNlIHNpbXBsZSBhdXRo
ZW50aWNhdGlvbiBvZiB0aGUgb3JpZ2luYXRvciB0bw0KICAgZXN0YWJsaXNoIGFuZCB2ZXJp
ZnkgdGhlaXIgaWRlbnRpdHkgYW5kIHRoZW4gY2hlY2sgdGhlIGlkZW50aXR5DQogICBhZ2Fp
bnN0IGEgcHJpdmF0ZSBhdXRob3JpemF0aW9uIHRhYmxlLg0KDQogICBPcmlnaW5hdG9yIGF1
dGhlbnRpY2F0aW9uIGVudGFpbHMgdGhlIHVzZSBvZiB3ZWFrIG9yIHN0cm9uZw0KICAgbWVj
aGFuaXNtcywgc3VjaCBhcyBjbGVhcnRleHQga2V5d29yZHMgb3IgZW5jcnlwdGlvbi1iYXNl
ZCBkYXRhLQ0KICAgc2lnbmluZywgcmVzcGVjdGl2ZWx5LCB0byBkZXRlcm1pbmUgYW5kIHZh
bGlkYXRlIHRoZSBpZGVudGlmeSBvZiB0aGUNCiAgIHNlbmRlciBhbmQgYXNzZXNzIHBlcm1p
c3Npb25zIGFjY29yZGluZ2x5Lg0KDQogICBPdGhlciBjb250cm9sIG1lY2hhbmlzbXMgd2hp
Y2ggYXJlIGNvbW1vbiBpbmNsdWRlIHNvdXJjZSBmaWx0ZXJpbmcNCiAgIGFuZCBvcmlnaW5h
dG9yIGF1dGhlbnRpY2F0aW9uLiAgU291cmNlIGZpbHRlcmluZyBlbnRhaWxzIG9mZnJhbXAN
CiAgIGdhdGV3YXkgdmVyaWZpY2F0aW9uIG9mIHRoZSBob3N0IG9yIG5ldHdvcmsgb3JpZ2lu
YXRpbmcgdGhlIG1lc3NhZ2UNCiAgIGFuZCBwZXJtaXR0aW5nIG9yIHByb2hpYml0aW5nIHJl
bGF5aW5nIGFjY29yZGluZ2x5Lg0KDQo1LjIuMyAgICAgR1NUTiBhdXRob3JpemF0aW9uIGlu
Zm9ybWF0aW9uDQoNCiAgIENvbmZpZGVudGlhbCBpbmZvcm1hdGlvbiBhYm91dCB0aGUgc2Vu
ZGVyIG5lY2Vzc2FyeSB0byBkaWFsIGEgRzNGYXgNCiAgIHJlY2lwaWVudCwgc3VjaCBhcyBz
ZW5kZXIncyBjYWxsaW5nIGNhcmQgYXV0aG9yaXphdGlvbiBudW1iZXIsIG1pZ2h0DQogICBi
ZSBkaXNjbG9zZWQgdG8gdGhlIEczRmF4IHJlY2lwaWVudCAob24gdGhlIGNvdmVyIHBhZ2Up
LCBzdWNoIGFzDQogICB0aHJvdWdoIHBhcmFtZXRlcnMgZW5jb2RlZCBpbiB0aGUgRzNGYXgg
cmVjaXBpZW50cyBhZGRyZXNzIGluIHRoZSBUbzoNCiAgIG9yIENDOiBmaWVsZHMuDQoNCiAg
IFNlbmRlcnMgU0hPVUxEIGJlIHByb3ZpZGVkIHdpdGggYSBtZXRob2Qgb2YgcHJldmVudGlu
ZyBzdWNoDQogICBkaXNjbG9zdXJlLiAgQXMgd2l0aCBtZWNoYW5pc21zIGZvciBoYW5kbGlu
ZyB1bnNvbGljaXRlZCBmYXhlcywgdGhlcmUNCiAgIGFyZSBub3QgeWV0IHN0YW5kYXJkIG1l
Y2hhbmlzbXMgZm9yIHByb3RlY3Rpbmcgc3VjaCBpbmZvcm1hdGlvbi4NCiAgIE91dC1vZi1i
YW5kIGNvbW11bmljYXRpb24gb2YgYXV0aG9yaXphdGlvbiBpbmZvcm1hdGlvbiBvciB1c2Ug
b2YNCiAgIGVuY3J5cHRlZCBkYXRhIGluIHNwZWNpYWwgZmllbGRzIGFyZSB0aGUgYXZhaWxh
YmxlIG5vbi1zdGFuZGFyZA0KICAgdGVjaG5pcXVlcy4NCg0KICAgVHlwaWNhbGx5IGF1dGhv
cml6YXRpb24gbmVlZHMgdG8gYmUgYXNzb2NpYXRlZCB0byBzcGVjaWZpYyBzZW5kZXJzDQog
ICBhbmQgc3BlY2lmaWMgbWVzc2FnZXMsIGluIG9yZGVyIHRvIHByZXZlbnQgYSAicmVwbGF5
IiBhdHRhY2sgd2hpY2gNCiAgIGNhdXNlcyBhbmQgZWFybGllciBhdXRob3JpemF0aW9uIHRv
IGVuYWJsZSBhIGxhdGVyIGRpYWwtb3V0IGJ5IGENCiAgIGRpZmZlcmVudCAoYW5kIHVuYXV0
aG9yaXplZCkgc2VuZGVyLiAgQSBub24tbWFsaWNpb3VzIGV4YW1wbGUgb2Ygc3VjaA0KDQoN
ClRveW9kYSwgZXQuIGFsLiAgICAgICAgICAgRXhwaXJlcyBKYW51YXJ5IDIwMDIgICAgICAg
ICAgICAgICAgICAgW1BhZ2UgN10NCgwNCkludGVybmV0IERyYWZ0ICAgICAgICAgIFNpbXBs
ZSBNb2RlIG9mIEZhY3NpbWlsZSAgICAgICAgICAgICAgIEp1bHkgMjAwMQ0KDQoNCg0KICAg
YSByZXBsYXkgd291bGQgYmUgdG8gaGF2ZSBhbiBlbWFpbCByZWNpcGllbnQgcmVwbHkgdG8g
YWxsIG9yaWdpbmFsDQogICByZWNpcGllbnRzIC0tIGluY2x1ZGluZyBhbiBvZmZyYW1wIElG
YXggcmVjaXBpZW50IC0tIGFuZCBoYXZlIHRoZQ0KICAgb3JpZ2luYWwgc2VuZGVyJ3MgYXV0
aG9yaXphdGlvbiBjYXVzZSB0aGUgcmVwbHkgdG8gYmUgc2VudC4NCg0KNS4yLjQgICAgIFNl
bmRlciBhY2NvdW50YWJpbGl0eQ0KDQogICBJbiBtYW55IGNvdW50cmllcywgdGhlcmUgaXMg
YSBsZWdhbCByZXF1aXJlbWVudCB0aGF0IHRoZSAic2VuZGVyIiBiZQ0KICAgZGlzY2xvc2Vk
IG9uIGEgZmFjc2ltaWxlIG1lc3NhZ2UuICBFbWFpbCBGcm9tIGFkZHJlc3NlcyBhcmUgdHJp
dmlhbA0KICAgdG8gZmFrZSwgc28gdGhhdCB1c2luZyBvbmx5IHRoZSBNQUlMIEZST00gWzEs
IDNdICBvciBGcm9tIFsyLCAzXQ0KICAgaGVhZGVyIGlzIG5vdCBzdWZmaWNpZW50Lg0KDQog
ICBPZmZyYW1wcyBTSE9VTEQgZW5zdXJlIHRoYXQgdGhlIHJlY2lwaWVudCBpcyBwcm92aWRl
ZCBjb250YWN0DQogICBpbmZvcm1hdGlvbiBhYm91dCB0aGUgb2ZmcmFtcCwgaW4gdGhlIGV2
ZW50IG9mIHByb2JsZW1zLg0KDQogICBUaGUgRzNGYXggcmVjaXBpZW50IFNIT1VMRCBiZSBw
cm92aWRlZCB3aXRoIHN1ZmZpY2llbnQgaW5mb3JtYXRpb24NCiAgIHdoaWNoIHBlcm1pdHMg
dHJhY2luZyB0aGUgb3JpZ2luYXRvciBvZiB0aGUgSUZheCBtZXNzYWdlLiAgU3VjaA0KICAg
aW5mb3JtYXRpb24gbWlnaHQgaW5jbHVkZSB0aGUgY29udGVudHMgb2YgdGhlIE1BSUwgRlJP
TSwgRnJvbSwgU2VuZGVyDQogICBhbmQgUmVwbHktVG8gaGVhZGVycywgYXMgd2VsbCBhcyBN
ZXNzYWdlLUlkIGFuZCBSZWNlaXZlZCBoZWFkZXJzLg0KDQo1LjIuNSAgICAgTWVzc2FnZSBk
aXNjbG9zdXJlDQoNCiAgIFVzZXJzIG9mIEczRmF4IGRldmljZXMgaGF2ZSBhbiBleHBlY3Rh
dGlvbiBvZiBhIGxldmVsIG9mIG1lc3NhZ2UNCiAgIHByaXZhY3kgd2hpY2ggaXMgaGlnaGVy
IHRoYW4gdGhlIGxldmVsIHByb3ZpZGVkIGJ5IEludGVybmV0IG1haWwNCiAgIHdpdGhvdXQg
c2VjdXJpdHkgZW5oYW5jZW1lbnRzLg0KDQogICBUaGlzIGV4cGVjdGF0aW9uIG9mIHByaXZh
Y3kgYnkgRzNGYXggdXNlcnMgU0hPVUxEIGJlIHByZXNlcnZlZCBhcw0KICAgbXVjaCBhcyBw
b3NzaWJsZS4NCg0KICAgU3VmZmljaWVudCBwaHlzaWNhbCBhbmQgc29mdHdhcmUgY29udHJv
bCBtYXkgYmUgYWNjZXB0YWJsZSBpbg0KICAgY29uc3RyYWluZWQgZW52aXJvbm1lbnRzLiAg
VGhlIHVzdWFsIG1lY2hhbmlzbSBmb3IgZW5zdXJpbmcgZGF0YQ0KICAgY29uZmlkZW50aWFs
bHkgZW50YWlsIGVuY3J5cHRpb24sIGFzIGRpc2N1c3NlZCBiZWxvdy4NCg0KNS4yLjYgICAg
IE5vbiBwcml2YXRlIG1haWxib3hlcw0KDQogICBXaXRoIGVtYWlsLCBib3VuY2VzIChkZWxp
dmVyeSBmYWlsdXJlcykgYXJlIHR5cGljYWxseSByZXR1cm5lZCB0byB0aGUNCiAgIHNlbmRl
ciBhbmQgbm90IHRvIGEgcHVibGljbHktYWNjZXNzaWJsZSBlbWFpbCBhY2NvdW50IG9yIHBy
aW50ZXIuDQogICBXaXRoIGZhY3NpbWlsZSwgYm91bmNlcyBkbyBub3QgdHlwaWNhbGx5IG9j
Y3VyLiAgSG93ZXZlciwgd2l0aCBJRmF4LA0KICAgYSBib3VuY2UgY291bGQgYmUgc2VudCBl
bHNld2hlcmUgKHNlZSBzZWN0aW9uIFtEZWxpdmVyeSBGYWlsdXJlXSksDQogICBzdWNoIGFz
IGEgbG9jYWwgc3lzdGVtIGFkbWluaXN0cmF0b3IncyBhY2NvdW50LCBwdWJsaWNseS1hY2Nl
c3NpYmxlDQogICBhY2NvdW50LCBvciBhbiBJRmF4IHByaW50ZXIgKHNlZSBhbHNvIFtUcmFm
ZmljIEFuYWx5c2lzXSkuDQoNCjUuMi43ICAgICBUcmFmZmljIGFuYWx5c2lzDQoNCiAgIEVh
dmVzZHJvcHBpbmcgb2Ygc2VuZGVycyBhbmQgcmVjaXBpZW50cyBpcyBlYXNpZXIgb24gdGhl
IEludGVybmV0DQogICB0aGFuIEdTVE4uICBOb3RlIHRoYXQgbWVzc2FnZSBvYmplY3QgZW5j
cnlwdGlvbiBkb2VzIG5vdCBwcmV2ZW50DQogICB0cmFmZmljIGFuYWx5c2lzLCBidXQgY2hh
bm5lbCBzZWN1cml0eSBjYW4gaGVscCB0byBmcnVzdHJhdGUgYXR0ZW1wdHMNCiAgIGF0IHRy
YWZmaWMgYW5hbHlzaXMuDQoNCg0KDQoNClRveW9kYSwgZXQuIGFsLiAgICAgICAgICAgRXhw
aXJlcyBKYW51YXJ5IDIwMDIgICAgICAgICAgICAgICAgICAgW1BhZ2UgOF0NCgwNCkludGVy
bmV0IERyYWZ0ICAgICAgICAgIFNpbXBsZSBNb2RlIG9mIEZhY3NpbWlsZSAgICAgICAgICAg
ICAgIEp1bHkgMjAwMQ0KDQoNCg0KNS4zIFNlY3VyaXR5IFRlY2huaXF1ZXMNCg0KICAgVGhl
cmUgYXJlIHR3byBiYXNpYyBhcHByb2FjaGVzIHRvIGVuY3J5cHRpb24tYmFzZWQgc2VjdXJp
dHkgd2hpY2gNCiAgIHN1cHBvcnQgYXV0aGVudGljYXRpb24gYW5kIHByaXZhY3k6DQoNCjUu
My4xICAgICBDaGFubmVsIHNlY3VyaXR5DQoNCiAgIEFzIHdpdGggYWxsIGVtYWlsLCBhbiBJ
RmF4IG1lc3NhZ2UgY2FuIGJlIHZpZXdlZCBhcyBpdCB0cmF2ZXJzZXMNCiAgIGludGVybmFs
IG5ldHdvcmtzIG9yIHRoZSBJbnRlcm5ldCBpdHNlbGYuDQoNCiAgVmlydHVhbCBQcml2YXRl
IE5ldHdvcmtzIChWUE4pLCBlbmNyeXB0ZWQgdHVubmVscywgb3IgdHJhbnNwb3J0DQogIGxh
eWVyIHNlY3VyaXR5IGNhbiBiZSB1c2VkIHRvIHByZXZlbnQgZWF2ZXNkcm9wcGluZyBvZiBh
IG1lc3NhZ2UNCiAgYXMgaXQgdHJhdmVyc2VzIHN1Y2ggbmV0d29ya3MuICBJdCBhbHNvIHBy
b3ZpZGVzIHNvbWUgcHJvdGVjdGlvbg0KICBhZ2FpbnN0IHRyYWZmaWMgYW5hbHlzaXMsIGFz
IGRlc2NyaWJlZCBhYm92ZS4NCg0KICBBdCB0aGUgY3VycmVudCB0aW1lIHZhcmlvdXMgcHJv
dG9jb2xzIGV4aXN0IGZvciBwZXJmb3JtaW5nIHRoZSBhYm92ZQ0KICBmdW5jdGlvbnMsIGFu
ZCBhcmUgb25seSBtZW50aW9uZWQgaGVyZSBmb3IgaW5mb3JtYXRpb24uICBTdWNoIHByb3Rv
Y29scw0KICBhcmUgSVBTZWMgWzE3XSBhbmQgVExTIFsxOF0uDQoNCjUuMy4yICAgICBPYmpl
Y3Qgc2VjdXJpdHkNCg0KICAgQXMgd2l0aCBhbGwgZW1haWwsIGFuIElGYXggbWVzc2FnZSBj
YW4gYmUgdmlld2VkIHdoaWxlIGl0IHJlc2lkZXMgb24sDQogICBvciB3aGlsZSBpdCBpcyBy
ZWxheWVkIHRocm91Z2gsIGFuIGludGVybWVkaWF0ZSBNYWlsIFRyYW5zZmVyIEFnZW50Lg0K
ICANCiAgTWVzc2FnZSBlbmNyeXB0aW9uIGNhbiBiZSB1c2VkIHRvIHByb3ZpZGUgZW5kLXRv
LWVuZCBlbmNyeXB0aW9uLg0KICANCiAgQXQgdGhlIGN1cnJlbnQgdGltZSB0d28gcHJvdG9j
b2xzIGFyZSBjb21tb25seSB1c2VkIGZvciBtZXNzYWdlDQogIGVuY3J5cHRpb24gYW5kIGFy
ZSBvbmx5IG1lbnRpb25lZCBoZXJlIGZvciBpbmZvcm1hdGlvbi4gIFRoZSB0d28NCiAgcHJv
dG9jb2xzIGFyZSBQR1AtTUlNRSBbMTZdIGFuZCBTL01JTUUgWzE5XS4NCg0KNiAgUkVGRVJF
TkNFUw0KDQo2LjEgTm9ybWF0aXZlIHJlZmVyZW5jZXMNCg0KICAgWzFdICBQb3N0ZWwsIEou
LCAiU2ltcGxlIE1haWwgVHJhbnNmZXIgUHJvdG9jb2wiLCBTVEQgMTAsIFJGQw0KICAgICAg
ICA4MjEsIEF1Z3VzdCAxOTgyLg0KDQogICBbMl0gIENyb2NrZXIsIEQuLCAiU3RhbmRhcmQg
Zm9yIHRoZSBGb3JtYXQgb2YgQVJQQSBJbnRlcm5ldA0KICAgICAgICBUZXh0IE1lc3NhZ2Vz
IiwgU1REIDExLCBSRkMgODIyLCBBdWd1c3QgbDk4Mi4NCg0KICAgWzNdICBCcmFkZW4sIFIu
LCAxMTIzICJSZXF1aXJlbWVudHMgZm9yIEludGVybmV0IGhvc3RzIC0NCiAgICAgICAgYXBw
bGljYXRpb24gYW5kIHN1cHBvcnQiLCBSRkMgMTEyMywgT2N0b2JlciAxOTg5Lg0KDQogICBb
NF0gIEJvcmVuc3RlaW4sIE4uLCBhbmQgTi4gRnJlZWQsICIgTXVsdGlwdXJwb3NlIEludGVy
bmV0DQogICAgICAgIE1haWwgRXh0ZW5zaW9ucyAoTUlNRSkgUGFydCBGaXZlOiAgQ29uZm9y
bWFuY2UgQ3JpdGVyaWEgYW5kDQogICAgICAgIEV4YW1wbGVzICIsIFJGQyAyMDQ5LCBOb3Zl
bWJlciAxOTk2Lg0KDQogICBbNV0gIE1jSW50eXJlLCBMLiwgWmlsbGVzLCBTLiwgQnVja2xl
eSwgUi4sIFZlbmFibGUsIEQuLA0KICAgICAgICBQYXJzb25zLCBHLiwgYW5kIEouIFJhZmZl
cnR5LCAiRmlsZSBGb3JtYXQgZm9yIEludGVybmV0IEZheCIsDQogICAgICAgIFJGQyAyMzAx
LCBNYXJjaCAxOTk4Lg0KDQoNClRveW9kYSwgZXQuIGFsLiAgICAgICAgICAgRXhwaXJlcyBK
YW51YXJ5IDIwMDIgICAgICAgICAgICAgICAgICAgW1BhZ2UgOV0NCgwNCkludGVybmV0IERy
YWZ0ICAgICAgICAgIFNpbXBsZSBNb2RlIG9mIEZhY3NpbWlsZSAgICAgICAgICAgICAgIEp1
bHkgMjAwMQ0KDQoNCg0KICAgWzZdICBNeWVycywgSi4sIGFuZCBNLiBSb3NlLCAiUG9zdCBP
ZmZpY2UgUHJvdG9jb2wgLSBWZXJzaW9uDQogICAgICAgIDMiLCBTVEQgNTMsIFJGQyAxOTM5
LCBNYXkgMTk5Ni4NCg0KICAgWzddICBBbGxvY2NoaW8sIEMuLCAiTWluaW1hbCBQU1ROIGFk
ZHJlc3MgZm9ybWF0IGZvciBJbnRlcm5ldA0KICAgICAgICBtYWlsIiwgZHJhZnQtaWV0Zi1m
YXgtZmF4YWRkci12Mi0wNC50eHQsIEp1bmUgMjAwMS4NCiAgICAgICAgDQogICBbOF0gIEFs
bG9jY2hpbywgQy4sICJNaW5pbWFsIGZheCBhZGRyZXNzIGZvcm1hdCBmb3IgSW50ZXJuZXQN
CiAgICAgICAgbWFpbCIsIGRyYWZ0LWlldGYtZmF4LW1pbmFkZHItdjItMDQudHh0LCBKdW5l
IDIwMDEuICAgICAgICANCg0KICAgWzldICBNb29yZSwgSy4sIGFuZCBHLiBWYXVkcmV1aWws
ICJBbiBFeHRlbnNpYmxlIE1lc3NhZ2UNCiAgICAgICAgRm9ybWF0IGZvciBEZWxpdmVyeSBT
dGF0dXMgTm90aWZpY2F0aW9ucyIsIFJGQyAxODk0LCBKYW51YXJ5DQogICAgICAgIDE5OTYu
DQoNCiAgIFsxMF0gRnJlZWQsIE4uLCBhbmQgTi4gQm9yZW5zdGVpbiwgIk11bHRpcHVycG9z
ZSBJbnRlcm5ldA0KICAgICAgICBNYWlsIEV4dGVuc2lvbnMgKE1JTUUpIFBhcnQgVHdvOiBN
ZWRpYSBUeXBlcyIsIFJGQyAyMDQ2LA0KICAgICAgICBOb3ZlbWJlciAxOTk2Lg0KDQogICBb
MTFdIE1vb3JlLCBLLiwgIk1JTUUgKE11bHRpcHVycG9zZSBJbnRlcm5ldCBNYWlsIEV4dGVu
c2lvbnMpIFBhcnQNCiAgICAgICAgVGhyZWU6IE1lc3NhZ2UgSGVhZGVyIEV4dGVuc2lvbnMg
Zm9yIE5vbi1BU0NJSSBUZXh0IiwgUkZDIDIwNDcsDQogICAgICAgIE5vdmVtYmVyIDE5OTYu
DQoNCiAgIFsxMl0gUGFyc29ucywgRy4gYW5kIFJhZmZlcnR5LCBKLiwgIlRhZyBJbWFnZSBG
aWxlIEZvcm1hdA0KICAgICAgICAoVElGRikgLS0gaW1hZ2UvVElGRjogTUlNRSBTdWItdHlw
ZSBSZWdpc3RyYXRpb24iLCBSRkMgMjMwMiwNCiAgICAgICAgTWFyY2ggMTk5OC4NCg0KICAg
WzEzXSAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNzIHRvIEluZGlj
YXRlDQogICAgICAgIFJlcXVpcmVtZW50IExldmVscyIsIFJGQyAyMTE5LCBNYXJjaCAxOTk3
Lg0KDQoNCjYuMiAgTm9uLW5vcm1hdGl2ZSByZWZlcmVuY2VzDQoNCiAgIFsxNF0gIFBhcnNv
bnMsIEcuLCBhbmQgSi4gUmFmZmVydHksICJUYWcgSW1hZ2UgRmlsZSBGb3JtYXQNCiAgICAg
ICAgKFRJRkYpIC0tIEYgUHJvZmlsZSBmb3IgRmFjc2ltaWxlIiwgUkZDIDIzMDYsIE1hcmNo
IDE5OTguDQoNCiAgIFsxNV0gIElUVS1UIChDQ0lUVCksICJTdGFuZGFyZGl6YXRpb24gb2Yg
R3JvdXAgMyBmYWNzaW1pbGUNCiAgICAgICAgYXBwYXJhdHVzIGZvciBkb2N1bWVudCB0cmFu
c21pc3Npb24iLCBJVFUtVCAoQ0NJVFQpLA0KICAgICAgICBSZWNvbW1lbmRhdGlvbiBULjQu
DQoNCiAgIFsxNl0gQ2FsbGFzLCBKLiwgRG9ubmVyaGFja2UsIEwuLCBGaW5uZXksIEguLCBh
bmQgVGhheWVyLCBSLiwNCiAgICAgICAgIk9wZW5QR1AgTWVzc2FnZSBGb3JtYXQiLCBSRkMg
MjQ0MCwgTm92ZW1iZXIgMTk5OA0KDQogICBbMTddIEtlbnQsIFMuIGFuZCBBdGtpbnNvbiwg
Ui4sICJTZWN1cml0eSBBcmNoaXRlY3R1cmUgZm9yIHRoZQ0KICAgICAgICBJbnRlcm5ldCBQ
cm90b2NvbCIsIFJGQyAyNDAxLCBOb3ZlbWJlciAxOTk4Lg0KDQogICBbMThdIEhvZmZtYW4s
IFAuLCAiU01UUCBTZXJ2aWNlIEV4dGVuc2lvbiBmb3IgU2VjdXJlIFNNVFAgb3ZlciBUTFMi
LA0KICAgICAgICBSRkMgMjQ4NywgSmFudWFyeSAxOTk5Lg0KDQogICBbMTldIER1c3NlLCBT
LiwgSG9mZm1hbiwgUC4sIFJhbXNkZWxsLCBCLiwgTHVuZGJsYWRlLCBMLiwgYW5kDQogICAg
ICAgIEwuIFJlcGthLCAiUy9NSU1FIFZlcnNpb24gMiBNZXNzYWdlIFNwZWNpZmljYXRpb24i
LCBSRkMgMjMxMSwNCiAgICAgICAgTWFyY2ggMTk5OC4NCg0KDQpUb3lvZGEsIGV0LiBhbC4g
ICAgICAgICAgIEV4cGlyZXMgSmFudWFyeSAyMDAyICAgICAgICAgICAgICAgICAgIFtQYWdl
IDEwXQ0KDA0KSW50ZXJuZXQgRHJhZnQgICAgICAgICAgU2ltcGxlIE1vZGUgb2YgRmFjc2lt
aWxlICAgICAgICAgICAgICAgSnVseSAyMDAxDQoNCg0KDQo3ICBBQ0tOT1dMRURHRU1FTlRT
DQoNCiAgIFRoaXMgc3BlY2lmaWNhdGlvbiB3YXMgcHJvZHVjZWQgYnkgdGhlIEludGVybmV0
IEVuZ2luZWVyaW5nIFRhc2sNCiAgIEZvcmNlIEZheCBXb3JraW5nIEdyb3VwLCBvdmVyIHRo
ZSBjb3Vyc2Ugb2YgbW9yZSB0aGFuIG9uZSB5ZWFyJ3MNCiAgIG9ubGluZSBhbmQgZmFjZS10
by1mYWNlIGRpc2N1c3Npb25zLiAgQXMgd2l0aCBhbGwgSUVURiBlZmZvcnRzLCBtYW55DQog
ICBwZW9wbGUgY29udHJpYnV0ZWQgdG8gdGhlIGZpbmFsIHByb2R1Y3QuDQoNCiAgIEFjdGl2
ZSBmb3IgdGhpcyBkb2N1bWVudCB3ZXJlOiBTdGV2ZSBIdXN0b24sIEplZmZyZXkgUGVycnks
IEdyZWcNCiAgIFZhdWRyZXVpbCwgUmljaGFyZCBTaG9ja2V5LCBDaGFybGVzIFd1LCBHcmFo
YW0gS2x5bmUsIFJvYmVydCBBLg0KICAgUm9zZW5iZXJnLCBMYXJyeSBNYXNpbnRlciwgRGF2
ZSBDcm9ja2VyLCBIZXJtYW4gU2lsYmlnZXIsIEphbWVzDQogICBSYWZmZXJ0eS4NCg0KOCAg
QVVUSE9SUycgQUREUkVTU0VTDQoNCiAgIEtpeW9zaGkgVG95b2RhDQogICBNYXRzdXNoaXRh
IEdyYXBoaWMgQ29tbXVuaWNhdGlvbiBTeXN0ZW1zLCBJbmMuDQogICAyLTMtOCBTaGltb21l
Z3VybywgTWVndXJvLWt1DQogICBUb2t5byAxNTMgSmFwYW4NCiAgIEZheDogKzgxIDMgNTQz
NCA3MTY2DQogICBFbWFpbDoga3RveW9kYUByZG1nLm1nY3MubWVpLmNvLmpwDQoNCiAgIEhp
cm95dWtpIE9obm8NCiAgIENvbW11bmljYXRpb25zIFJlc2VhcmNoIExhYm9yYXRvcnkuDQog
ICA0LTItMSwgTnVrdWktS2l0YW1hY2hpLCBLb2dhbmVpLCBUb2t5bywNCiAgIDE4NC04Nzk1
LCBKYXBhbg0KICAgRkFYOiArODEgNDIgMzI3IDc5NDENCiAgIEVtYWlsOiBob2hub0BvaG5v
bGFiLm9yZw0KDQogICBKdW4gTXVyYWkNCiAgIEtlaW8gVW5pdmVyc2l0eQ0KICAgNTMyMiBF
bmRvLCBGdWppc2F3YQ0KICAgS2FuYWdhd2EgMjUyIEphcGFuDQogICBGYXg6ICs4MSA0NjYg
NDkgMTEwMQ0KICAgRW1haWw6IGp1bkB3aWRlLmFkLmpwDQoNCiAgIERhbiBXaW5nDQogICAx
NzAgVy4gVGFzbWFuIERyaXZlDQogICBTYW4gSm9zZSwgQ0EgOTUxMzQNCiAgIFBob25lOiAr
MSA0MDggNTI1IDUzMTQNCiAgIEVtYWlsOiBkd2luZ0BjaXNjby5jb20NCg0KDQoNCg0KDQoN
Cg0KDQoNCg0KDQpUb3lvZGEsIGV0LiBhbC4gICAgICAgICAgIEV4cGlyZXMgSmFudWFyeSAy
MDAyICAgICAgICAgICAgICAgICAgIFtQYWdlIDExXQ0KDA0KSW50ZXJuZXQgRHJhZnQgICAg
ICAgICAgU2ltcGxlIE1vZGUgb2YgRmFjc2ltaWxlICAgICAgICAgICAgICAgSnVseSAyMDAx
DQoNCg0KDQo5IEFQUEVORElYIEE6ICBFeGNlcHRpb25zIHRvIE1JTUUNCg0KICAgKiAgICBJ
RmF4IHNlbmRlcnMgYXJlIG5vdCByZXF1aXJlZCB0byBiZSBhYmxlIHRvIHNlbmQNCiAgICAg
ICAgdGV4dC9wbGFpbiBtZXNzYWdlcyAoUkZDIDIwNDkgcmVxdWlyZW1lbnQgNCksIGFsdGhv
dWdoIElGYXgNCiAgICAgICAgcmVjaXBpZW50cyBhcmUgcmVxdWlyZWQgdG8gYWNjZXB0IHN1
Y2ggbWVzc2FnZXMsIGFuZCB0byBwcm9jZXNzDQogICAgICAgIHRoZW0uDQoNCiAgICogICAg
SUZheCByZWNpcGllbnRzIGFyZSBub3QgcmVxdWlyZWQgdG8gb2ZmZXIgdG8gcHV0IHJlc3Vs
dHMNCiAgICAgICAgaW4gIGEgZmlsZS4gKEFsc28gc2VlIDIuMy4yLikNCg0KICAgKiAgICBJ
RmF4IHJlY2lwaWVudHMgTUFZIGRpcmVjdGx5IHByaW50L2ZheCAgdGhlIHJlY2VpdmVkDQog
ICAgICAgIG1lc3NhZ2UgcmF0aGVyICB0aGFuICJkaXNwbGF5IiBpdCwgYXMgaW5kaWNhdGVk
IGluIFJGQyAyMDQ5Lg0KDQoNCjEwIEFQUEVORElYIEI6ICBMaXN0IG9mIGVkaXRzIHRvIFJG
QzIzMDUgDQoNCiAgICstLS0tKy0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCiAgIHwgTm8ufCBTZWN0aW9uICB8ICAgICAg
ICAgICAgIEVkaXQgIEp1bHkgMjcsIDIwMDEgICAgICAgICAgICAgICAgIHwNCiAgICstLS0t
Ky0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLSsNCiAgIHwgMS4gfENvcHlyaWdodCB8IFVwZGF0ZWQgY29weXJpaGdodCBmcm9t
ICIxOTk4IiB0byAiMTk5OSwyMDAwIiAgIHwgIA0KICAgfCAgICB8Tm90aWNlICAgIHwgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgKy0t
LS0rLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tKw0KICAgfCAyLiB8U1VNTUFSWSAgIHwgQ2hhbmdlZCB0aGUgcGhyYXNlICJv
dmVyIHRoZSBJbnRlcm5ldCIgdG8gICAgICAgfA0KICAgfCAgICB8ICAgICAgICAgIHwgICAg
ICAgICAgICAgICAidXNpbmcgSW50ZXJuZXQgbWFpbCIgICAgICAgICAgICAgfA0KICAgKy0t
LS0rLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tKw0KICAgfCAzLiB8NSAgICAgICAgIHwgQ2hhbmdlZCB0aGUgcGFyYWdyYXBo
cyByZWdhcmRpbmcgdG8gdGhlICAgICAgICAgfA0KICAgfCAgICB8ICAgICAgICAgIHwgZm9s
bG93aW5nIHJlZmVyZW5jZXMgdG8gbWFrZSB0aGVtIHZlcnkgICAgICAgICAgfA0KICAgfCAg
ICB8ICAgICAgICAgIHwgbm9uLW5vcm1hdGl2ZS4gICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgfA0KICAgfCAgICB8ICAgICAgICAgIHwgICJPcGVuUEdQIE1lc3NhZ2UgRm9y
bWF0IiwgUkZDMjQ0MCAgICAgICAgICAgICAgfA0KICAgfCAgICB8ICAgICAgICAgIHwgICJT
ZWN1cml5IEFyY2hpdGVjdHVyZSBmb3IgdGhlIElQIiwgUkZDMjQwMSAgICAgfA0KICAgfCAg
ICB8ICAgICAgICAgIHwgICJTTVRQIFNlcnZpY2UgRXh0ZW5zaW9ucyBmb3IgU2VjdXJlIFNN
VFAgb3ZlciAgfA0KICAgfCAgICB8ICAgICAgICAgIHwgICBUTFMiLCBSRkMyNDg3ICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgfCAgICB8ICAgICAgICAgIHwgICJT
L01JTUUgVmVyc2lvbiAyIE1lc3NhZ2UgU3BlY2lmaWNhdGlvbiIsICAgICAgfA0KICAgfCAg
ICB8ICAgICAgICAgIHwgICBSRkMyMzExICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgfA0KICAgKy0tLS0rLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKw0KICAgfCA0LiB8UkVGRVJFTkNFU3wgUmVt
b3ZlZCB0aGUgZm9sbG93aW5nIHJlZmVyZW5jZXMgYmVjYXVzZSB0aGV5ICAgfA0KICAgfCAg
ICB8ICAgICAgICAgIHwgYXJlIG5vbi1ub21hcnRpdmUgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgfA0KICAgfCAgICB8ICAgICAgICAgIHwgICJTTVRQIFNlcnZpY2UgRXh0ZW5z
aW9ucyBmb3IgRGVsaXZlcnkgU3RhdHVzICAgfCAgICAgICAgICAgICB8ICAgIHwgICAgICAg
ICAgfCAgIE5vdGlmaWNhdGlvbnMiLCBSRkMxODkxICAgICAgICAgICAgICAgICAgICAgICB8
DQogICB8ICAgIHwgICAgICAgICAgfCAgIkludGVybmV0IE1lc3NhZ2UgQWNjZXNzIFByb3Rv
Y29sIiwgUkZDMjA2MCAgICB8DQogICArLS0tLSstLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rDQogICB8IDUuIHxSRUZFUkVO
Q0VTfCBTZXBhcmF0ZWQgUkVGRVJFTkNFUyB0byB0aGUgbm9ybWF0aXZlIGFuZCAgICAgICB8
DQogICB8ICAgIHwgICAgICAgICAgfCBub24tbm9ybWF0aXZlICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICB8DQogICArLS0tLSstLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rDQogICB8IDYuIHxBcHBlbmRp
eCAgfCBDaGFuZ2VkIHRoZSBwaHJhc2UgZnJvbSAiTk9UIFJFUVVJUkVEIiB0byAgICAgICB8
DQogICB8ICAgIHwgQSAgICAgICAgfCAibm90IHJlcXVpcmVkIiAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICB8DQogICArLS0tLSstLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rDQogICB8IDcuIHxBcHBlbmRp
eCAgfCBBZGRlZCAiQXBwZW5kaXggQiAgTGlzdCBvZiBlZGl0cyB0byBSRkMyMzA1IiAgICB8
ICAgICAgICAgICAgICstLS0tKy0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSsNCg0KDQpUb3lvZGEsIGV0LiBhbC4gICAgICAg
ICAgIEV4cGlyZXMgSmFudWFyeSAyMDAyICAgICAgICAgICAgICAgICAgIFtQYWdlIDEyXQ0K
DA0KSW50ZXJuZXQgRHJhZnQgICAgICAgICAgU2ltcGxlIE1vZGUgb2YgRmFjc2ltaWxlICAg
ICAgICAgICAgICAgSnVseSAyMDAxDQoNCg0KDQoxMCAgRnVsbCBDb3B5cmlnaHQgU3RhdGVt
ZW50DQoNCiAgIENvcHlyaWdodCAoQykgVGhlIEludGVybmV0IFNvY2lldHkgKDE5OTkpLiAg
QWxsIFJpZ2h0cyBSZXNlcnZlZC4NCg0KICAgVGhpcyBkb2N1bWVudCBhbmQgdHJhbnNsYXRp
b25zIG9mIGl0IG1heSBiZSBjb3BpZWQgYW5kIGZ1cm5pc2hlZCB0bw0KICAgb3RoZXJzLCBh
bmQgZGVyaXZhdGl2ZSB3b3JrcyB0aGF0IGNvbW1lbnQgb24gb3Igb3RoZXJ3aXNlIGV4cGxh
aW4gaXQNCiAgIG9yIGFzc2lzdCBpbiBpdHMgaW1wbGVtZW50YXRpb24gbWF5IGJlIHByZXBh
cmVkLCBjb3BpZWQsIHB1Ymxpc2hlZA0KICAgYW5kIGRpc3RyaWJ1dGVkLCBpbiB3aG9sZSBv
ciBpbiBwYXJ0LCB3aXRob3V0IHJlc3RyaWN0aW9uIG9mIGFueQ0KICAga2luZCwgcHJvdmlk
ZWQgdGhhdCB0aGUgYWJvdmUgY29weXJpZ2h0IG5vdGljZSBhbmQgdGhpcyBwYXJhZ3JhcGgg
YXJlDQogICBpbmNsdWRlZCBvbiBhbGwgc3VjaCBjb3BpZXMgYW5kIGRlcml2YXRpdmUgd29y
a3MuICBIb3dldmVyLCB0aGlzDQogICBkb2N1bWVudCBpdHNlbGYgbWF5IG5vdCBiZSBtb2Rp
ZmllZCBpbiBhbnkgd2F5LCBzdWNoIGFzIGJ5IHJlbW92aW5nDQogICB0aGUgY29weXJpZ2h0
IG5vdGljZSBvciByZWZlcmVuY2VzIHRvIHRoZSBJbnRlcm5ldCBTb2NpZXR5IG9yIG90aGVy
DQogICBJbnRlcm5ldCBvcmdhbml6YXRpb25zLCBleGNlcHQgYXMgbmVlZGVkIGZvciB0aGUg
cHVycG9zZSBvZg0KICAgZGV2ZWxvcGluZyBJbnRlcm5ldCBzdGFuZGFyZHMgaW4gd2hpY2gg
Y2FzZSB0aGUgcHJvY2VkdXJlcyBmb3INCiAgIGNvcHlyaWdodHMgZGVmaW5lZCBpbiB0aGUg
SW50ZXJuZXQgU3RhbmRhcmRzIHByb2Nlc3MgbXVzdCBiZQ0KICAgZm9sbG93ZWQsIG9yIGFz
IHJlcXVpcmVkIHRvIHRyYW5zbGF0ZSBpdCBpbnRvIGxhbmd1YWdlcyBvdGhlciB0aGFuDQog
ICBFbmdsaXNoLg0KDQogICBUaGUgbGltaXRlZCBwZXJtaXNzaW9ucyBncmFudGVkIGFib3Zl
IGFyZSBwZXJwZXR1YWwgYW5kIHdpbGwgbm90IGJlDQogICByZXZva2VkIGJ5IHRoZSBJbnRl
cm5ldCBTb2NpZXR5IG9yIGl0cyBzdWNjZXNzb3JzIG9yIGFzc2lnbnMuDQoNCiAgIFRoaXMg
ZG9jdW1lbnQgYW5kIHRoZSBpbmZvcm1hdGlvbiBjb250YWluZWQgaGVyZWluIGlzIHByb3Zp
ZGVkIG9uIGFuDQogICAiQVMgSVMiIGJhc2lzIGFuZCBUSEUgSU5URVJORVQgU09DSUVUWSBB
TkQgVEhFIElOVEVSTkVUIEVOR0lORUVSSU5HDQogICBUQVNLIEZPUkNFIERJU0NMQUlNUyBB
TEwgV0FSUkFOVElFUywgRVhQUkVTUyBPUiBJTVBMSUVELCBJTkNMVURJTkcNCiAgIEJVVCBO
T1QgTElNSVRFRCBUTyBBTlkgV0FSUkFOVFkgVEhBVCBUSEUgVVNFIE9GIFRIRSBJTkZPUk1B
VElPTg0KICAgSEVSRUlOIFdJTEwgTk9UIElORlJJTkdFIEFOWSBSSUdIVFMgT1IgQU5ZIElN
UExJRUQgV0FSUkFOVElFUyBPRg0KICAgTUVSQ0hBTlRBQklMSVRZIE9SIEZJVE5FU1MgRk9S
IEEgUEFSVElDVUxBUiBQVVJQT1NFLg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KVG95b2RhLCBldC4gYWwuICAgICAgICAgICBFeHBpcmVzIEph
bnVhcnkgMjAwMiAgICAgICAgICAgICAgICAgICBbUGFnZSAxM10NCg0KDQoNCg==

----------------------3267630400572435--


From owner-ietf-fax@mail.imc.org  Wed Aug  1 22:33:18 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA18737
	for <fax-archive@odin.ietf.org>; Wed, 1 Aug 2001 22:33:15 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f721sit24798
	for ietf-fax-bks; Wed, 1 Aug 2001 18:54:44 -0700 (PDT)
Received: from pasiphae.eastgw.xerox.com (pasiphae.xerox.com [208.140.33.23])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f721shs24794
	for <ietf-fax@imc.org>; Wed, 1 Aug 2001 18:54:43 -0700 (PDT)
Received: from godzilla.ADOC.xerox.com (godzilla.ADOC.xerox.com [13.242.128.10])
	by pasiphae.eastgw.xerox.com (8.9.3/8.9.3) with ESMTP id VAA20267;
	Wed, 1 Aug 2001 21:54:41 -0400 (EDT)
Received: from mercury.adoc.xerox.com (mercury [13.242.100.20])
	by godzilla.ADOC.xerox.com (8.8.8+Sun/8.8.8/ADOC-HUB-1.7) with ESMTP id SAA20814;
	Wed, 1 Aug 2001 18:54:42 -0700 (PDT)
Received: by mercury.ADOC.xerox.com with Internet Mail Service (5.5.2653.19)
	id <PJRJ3JDZ>; Wed, 1 Aug 2001 18:54:42 -0700
Message-ID: <51B8ABCE456FD111899900805F6FD6EE067A34DB@mercury.ADOC.xerox.com>
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
To: "'wdknutsen@earthlink.net'" <wdknutsen@earthlink.net>
Cc: "'IETF fax WG'" <ietf-fax@imc.org>,
        "'William Rucklidge 1'"
	 <wjr@imarkets.com>
Subject: RE: TIFF-FX  ImageBaseColor's photometry
Date: Wed, 1 Aug 2001 18:54:31 -0700 
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


Dale,
Thank you for your review and comments.

As you have stated, there is benefit to be gained by relaxing the
ImageBaseColor constraints to accommodate use of the image data color
encoding parameters, as opposed to only ITULAB, to interpret ImageBaseColor
when the IFD contains image data. We explored many avenues to try and
accommodate this request but in the end concluded that it was not possible
to do so without creating issues for TIFF-FX base (i.e. RFC 2301 or a
revision of) readers. 

Our thought process follow the lines that ImageBaseColor relaxation may be
reasonably accommodated for TIFF-FX Extension Set 1 readers and writers.
This is, however, not true for TIFF-FX base readers, since there are
numerous TIFF-FX implementations deployed within the market and no way to
signal a change from default ITULAB interpretation of ImageBaseColor to that
of some other color space. The problem is manifested when a TIFF-FX base
reader unknowingly decodes a TIFF-FX Extension Set 1 file (unknowingly
because a TIFF-FX reader should ignore the unrecognized TIFF-FXExtension
field that accompanies all extension files) in which ImageBasecolor
interpretation is the only encoding change from a comparable TIFF-FX file.
The result is that the colors of the ImageBaseColor regions would be wrong
and the reader would have no way of predicting or detecting the error.

In conclusion we must regrettably deny your request to permit other color
spaces to be used in the interpretation of ImageBaseColor.

Regards,  
Lloyd

> -----Original Message-----
> From: Dale Knutsen [mailto:wdknutsen@earthlink.net]
> Sent: Saturday, July 28, 2001 10:25 AM
> To: ietf-fax@imc.org
> Subject: ImageBaseColor's photometry: Redefine to be simple, 
> convenient,
> practical
> 
> 
> 
> I am working on software implementing a TIFF-FX reader, and I
> have found the current definition of ImageBaseColor in TIFF-FX
> to be rather impractical, and I recommend changing it as
> described below.
> 
>     The Problem
> 
> The color sample data contained in the ImageBaseColor field is
> specified to be in photometry ITU L*a*b*. Notice that this
> photometry may be DIFFERENT than that of the image that is
> being represented. 
> 
> For example, consider TIFF generator software which has an
> input image with photometry CMYK; the software is rendering
> this image into a TIFF-FX data stream. If the generator notices
> a strip whose color is constant, the generator could achieve
> excellent compression by representing the constant color in
> ImageBaseColor and setting the strip byte count to zero.
> 
> HOWEVER, the generator is faced with the daunting task of
> representing the CMYK (in this example) constant color in ITU
> L*a*b* color space. This requires:
> 
> (a) the generator must have the mapping from device-dependent
> CMYK photometry to the colorimetric ITU L*a*b* photometry;
> typically this is done by having the appropriate ICC profile
> and applying it to the CMYK. However, the generator may not
> have the profile data available for a variety of reasons.
> 
> (b) the generator must incorporate the complicated algorithms
> (color space conversion, ICC profile processing) -- which are
> not required otherwise of the generator.
> 
> Similar problems occur to software reading a TIFF data stream. 
> 
>     Analysis and Proposal
> 
> It seems to me that the motivation behind of ImageBaseColor is
> to provide an efficient way to represent strips of constant
> color. Of course we want it to be simple and practical too --
> which I think the present definition is not. 
> 
> I propose that that the photometry and interpretation of the
> ImageBaseColor field data be changed to be IDENTICAL TO that of
> the containing IFD (including all applicable fields which
> modify the representation and photometric interpretation of
> color sample data). This means that the representation of
> ImageBaseColor sample data would be identical to the
> representation of the ordinary color sample data that it
> represents (stands in place of). This would be extremely simple
> and convenient, both for the creator of a TIFF data stream and
> for the reader of a TIFF data stream! There would be NO
> difference in the treatment of ordinary color sample data and
> the color sample data in the ImageBaseColor field. 
> 
> 
>     Dale Knutsen
> 
> -- 
> 
> 
> 
>     Dale Knutsen
> 
> 
> _______________________________________________
> Get your free email from http://webmail.earthlink.net
> 


From owner-ietf-fax@mail.imc.org  Thu Aug  2 02:04:06 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id CAA03754
	for <fax-archive@odin.ietf.org>; Thu, 2 Aug 2001 02:04:05 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f725UbJ29243
	for ietf-fax-bks; Wed, 1 Aug 2001 22:30:37 -0700 (PDT)
Received: from lysithea.eastgw.xerox.com (lysithea.xerox.com [208.140.33.22])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f725UYs29239
	for <ietf-fax@imc.org>; Wed, 1 Aug 2001 22:30:34 -0700 (PDT)
Received: from godzilla.ADOC.xerox.com (godzilla.ADOC.xerox.com [13.242.128.10])
	by lysithea.eastgw.xerox.com (8.9.3/8.9.3) with ESMTP id BAA14542;
	Thu, 2 Aug 2001 01:30:28 -0400 (EDT)
Received: from mercury.adoc.xerox.com (mercury [13.242.100.20])
	by godzilla.ADOC.xerox.com (8.8.8+Sun/8.8.8/ADOC-HUB-1.7) with ESMTP id WAA23261;
	Wed, 1 Aug 2001 22:30:24 -0700 (PDT)
Received: by mercury.ADOC.xerox.com with Internet Mail Service (5.5.2653.19)
	id <PJRJ3KLW>; Wed, 1 Aug 2001 22:30:23 -0700
Message-ID: <51B8ABCE456FD111899900805F6FD6EE067A34DD@mercury.ADOC.xerox.com>
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
To: "'IETF fax WG'" <ietf-fax@imc.org>
Cc: "'William Rucklidge 1'" <wjr@imarkets.com>,
        "'PWG - QualDocs DL'"
	 <ifx@pwg.org>,
        "'IBM - Ron Arps'" <arps@almaden.ibm.com>,
        "'Ono F. - Tokyo Institute of Polytechincs'" <ono@image.t-kougei.ac.jp>,
        "'ImagePower Steve Swift@imagepower'" <sswift@imagepower.com>,
        "'Abercrombie, Dave - personal'" <Dave@davengrace.com>
Subject: TIFF-FX Extension Set 1:  draft-mcintyre-tiff-fx-extension1-02
Date: Wed, 1 Aug 2001 22:30:22 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


All,

In Section E1.5.4, the SharedDataMemory entry of the Shared Data Entries
table, 2nd paragraph,
has two meanings associated with a "0" value, i) the required memory is not
know or ii) the field is not applicable.

Given that the buffering of shared data should always consume some memory,
it is reasonable to dispense with the second meaning. Accordingly the
paragraph is being edited by deleting the "or this field is not applicable"
portion. This provides a single "0" value meaning of required memory
unknown.              

Lloyd

************************************************
Lloyd McIntyre        lmcintyre@pahv.xerox.com
Xerox Corp., Xerox Architecture Center
3400 Hillview Ave. Bldg. 1
Palo Alto, CA 94304
Tel: +1 650 813 6762   fax: +1 650 813 6860
************************************************



From owner-ietf-fax@mail.imc.org  Thu Aug  2 05:27:30 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA18242
	for <fax-archive@odin.ietf.org>; Thu, 2 Aug 2001 05:27:29 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f728dBB23840
	for ietf-fax-bks; Thu, 2 Aug 2001 01:39:11 -0700 (PDT)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f728dAs23836
	for <ietf-fax@imc.org>; Thu, 2 Aug 2001 01:39:10 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-4.cisco.com (8.11.3/8.9.1) with ESMTP id f728dA313341;
	Thu, 2 Aug 2001 01:39:11 -0700 (PDT)
Received: from DWINGW2K (dhcp-rea-gp250-64-103-64-231.cisco.com [64.103.64.231])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAQ02381;
	Thu, 2 Aug 2001 01:38:59 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "IETF Internet Fax WG" <ietf-fax@imc.org>
Cc: "Conrad Price" <cprice@cisco.com>
Subject: NSF values
Date: Thu, 2 Aug 2001 09:38:59 +0100
Message-ID: <EOEBIJPEADOODFNEJPEGEEDOECAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Anyone know of a canonical list -- other than T.35 -- which lists 
NSF values assigned to each fax manufacturer?

-d




From owner-ietf-fax@mail.imc.org  Thu Aug  2 05:49:51 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA18905
	for <fax-archive@odin.ietf.org>; Thu, 2 Aug 2001 05:49:50 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7291jk27416
	for ietf-fax-bks; Thu, 2 Aug 2001 02:01:45 -0700 (PDT)
Received: from lancelot.crf.canon.fr (lancelot.crf.canon.fr [194.2.158.66])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7291hs27410
	for <ietf-fax@imc.org>; Thu, 2 Aug 2001 02:01:43 -0700 (PDT)
Received: (from smap@localhost)
	by lancelot.crf.canon.fr (8.9.2/8.9.2) id KAA22433
	for <ietf-fax@imc.org>; Thu, 2 Aug 2001 10:57:39 +0200 (MET DST)
X-Authentication-Warning: lancelot.crf.canon.fr: smap set sender to <maeda@crf.canon.fr> using -f
Received: from mercure.crf.canon.fr(intranet.crf.canon.fr 194.2.81.249) by lancelot via smap (V2.0beta)
	id xma022428; Thu, 2 Aug 01 10:57:10 +0200
Received: from crf.canon.fr ([194.2.81.21]) by
          mercure.crf.canon.fr (Netscape Messaging Server 4.15) with ESMTP
          id GHFMYY00.NAY; Thu, 2 Aug 2001 10:44:58 +0200 
Message-ID: <3B691677.D0193B28@crf.canon.fr>
Date: Thu, 02 Aug 2001 10:59:35 +0200
From: "MAEDA Toru" <maeda@crf.canon.fr>
Organization: Canon Research Centre France
X-Mailer: Mozilla 4.75 [ja] (Win98; U)
X-Accept-Language: ja
MIME-Version: 1.0
To: Claudio Allocchio <Claudio.Allocchio@garr.it>, ietf <ietf-fax@imc.org>,
        tamura <tamura@toda.ricoh.co.jp>
Subject: Absence of fax-wg at London
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Hi, folks, Claudio-san and Tamura-san

I am very sorry that I can not attend the fax-wg at London on 6 August.
We can discuss about drafts on the mailing list.

5.3 Terminal mode issue                     30 min       98
- draft-ietf-fax-terminal-mode-goals-00.txt
- draft-ietf-fax-terminal-mode-protocol-00.txt
- draft-ietf-fax-faxprocessing-status-00.txt


Regards.

-- 
***********************************
MAEDA TORU
Canon Research Centre France S.A.
***********************************


From owner-ietf-fax@mail.imc.org  Thu Aug  2 09:14:28 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA25979
	for <fax-archive@odin.ietf.org>; Thu, 2 Aug 2001 09:14:27 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f72CO4g07719
	for ietf-fax-bks; Thu, 2 Aug 2001 05:24:04 -0700 (PDT)
Received: from ws2-5.us4.outblaze.com (205-158-62-80.outblaze.com [205.158.62.80])
	by above.proper.com (8.11.3/8.11.3) with SMTP id f72CO2s07707
	for <ietf-fax@imc.org>; Thu, 2 Aug 2001 05:24:02 -0700 (PDT)
Received: (qmail 11752 invoked by uid 1001); 2 Aug 2001 12:23:54 -0000
Message-ID: <20010802122353.11751.qmail@earthlink.net>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from ws2-5.us4.outblaze.com for [209.179.192.44] via web-mailer
    on Thu, 02 Aug 2001 20:23:53 +0800
From: "Dale Knutsen" <wdknutsen@earthlink.net>
To: Lloyd.McIntyre@pahv.xerox.com,
        "wdknutsen@earthlink.net" <wdknutsen@earthlink.net>
Cc: "'IETF fax WG'" <ietf-fax@imc.org>
Date: Thu, 02 Aug 2001 20:23:53 +0800
Subject: RE: TIFF-FX  ImageBaseColor's photometry
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Lloyd,

Thanks for your thoughtful reply. I understand the
requirement for backward compatibility. And in that light I
offer the following proposal, which might be found to meet
all concerns.

In TIFF-FX Extension Set 1, define a new field, I'll call it
NewImageBaseColor, that is the same as ImageBaseColor except
that the photometry and interpretation of the
NewImageBaseColor field data is specified to be identical to
that of the containing IFD (including all applicable fields
which modify the representation and photometric
interpretation of color sample data).

For a writer of a TIFF-FX Extension Set 1 data set who
wishes to use NewImageBaseColor, to conform to the base
TIFF-FX standard the writer will include the standard
ImageBaseColor field as well as the NewImageBaseColor field.
This is no benefit to the writer, but it is extremely simple
and easy to do, and so adds negligible costs to the writer.

The benefit of the proposed change accrues to the reader of a
TIFF-FX Extension Set 1 data set, who may use the following
algorithm when dealing with a strip that has a strip byte
count of zero:

   IF NewImageBaseColor is present, then use its content to
   render the color in the color space of the image of which
   the strip is a part. This is simple, accurate, and very
   efficient.

   ELSE Use the ImageBaseColor field. If the color space of
   the image of which the strip is a part has photometry
   other than ITULAB, the reader must convert the
   ImageBaseColor data to the required output photometry.


As you know, I claim that this conversion (of ITULAB to an
arbitrary photometry) is onerous and problematical in many
system environments. Nevertheless, the addition of
NewImageBaseColor provides to readers of a TIFF-FX Extension
Set 1 data set an efficient, accurate, and simple way of
rendering fill colors in cases where the writer has utilized
NewImageBaseColor, while at the same time not significantly
increasing the complexity of software required to support
both TIFF-FX Extension Set 1 as well as the base TIFF-FX
standard.

    Dale Knutsen

-----Original Message-----
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
Date: Wed, 1 Aug 2001 18:54:31 -0700 
To: "'wdknutsen@earthlink.net'" <wdknutsen@earthlink.net>
Subject: RE: TIFF-FX  ImageBaseColor's photometry

> Dale,
> Thank you for your review and comments.
> 
> As you have stated, there is benefit to be gained by relaxing the
> ImageBaseColor constraints to accommodate use of the image data color
> encoding parameters, as opposed to only ITULAB, to interpret ImageBaseColor
> when the IFD contains image data. We explored many avenues to try and
> accommodate this request but in the end concluded that it was not possible
> to do so without creating issues for TIFF-FX base (i.e. RFC 2301 or a
> revision of) readers. 
> 
> Our thought process follow the lines that ImageBaseColor relaxation may be
> reasonably accommodated for TIFF-FX Extension Set 1 readers and writers.
> This is, however, not true for TIFF-FX base readers, since there are
> numerous TIFF-FX implementations deployed within the market and no way to
> signal a change from default ITULAB interpretation of ImageBaseColor to that
> of some other color space. The problem is manifested when a TIFF-FX base
> reader unknowingly decodes a TIFF-FX Extension Set 1 file (unknowingly
> because a TIFF-FX reader should ignore the unrecognized TIFF-FXExtension
> field that accompanies all extension files) in which ImageBasecolor
> interpretation is the only encoding change from a comparable TIFF-FX file.
> The result is that the colors of the ImageBaseColor regions would be wrong
> and the reader would have no way of predicting or detecting the error.
> 
> In conclusion we must regrettably deny your request to permit other color
> spaces to be used in the interpretation of ImageBaseColor.
> 
> Regards,  
> Lloyd
> 
> > -----Original Message-----
> > From: Dale Knutsen [mailto:wdknutsen@earthlink.net]
> > Sent: Saturday, July 28, 2001 10:25 AM
> > To: ietf-fax@imc.org
> > Subject: ImageBaseColor's photometry: Redefine to be simple, 
> > convenient,
> > practical
> > 
> > I am working on software implementing a TIFF-FX reader, and I
> > have found the current definition of ImageBaseColor in TIFF-FX
> > to be rather impractical, and I recommend changing it as
> > described below.
> > 
> >     The Problem
> > 
> > The color sample data contained in the ImageBaseColor field is
> > specified to be in photometry ITU L*a*b*. Notice that this
> > photometry may be DIFFERENT than that of the image that is
> > being represented. 
> > 
> > For example, consider TIFF generator software which has an
> > input image with photometry CMYK; the software is rendering
> > this image into a TIFF-FX data stream. If the generator notices
> > a strip whose color is constant, the generator could achieve
> > excellent compression by representing the constant color in
> > ImageBaseColor and setting the strip byte count to zero.
> > 
> > HOWEVER, the generator is faced with the daunting task of
> > representing the CMYK (in this example) constant color in ITU
> > L*a*b* color space. This requires:
> > 
> > (a) the generator must have the mapping from device-dependent
> > CMYK photometry to the colorimetric ITU L*a*b* photometry;
> > typically this is done by having the appropriate ICC profile
> > and applying it to the CMYK. However, the generator may not
> > have the profile data available for a variety of reasons.
> > 
> > (b) the generator must incorporate the complicated algorithms
> > (color space conversion, ICC profile processing) -- which are
> > not required otherwise of the generator.
> > 
> > Similar problems occur to software reading a TIFF data stream. 
> > 
> >     Analysis and Proposal
> > 
> > It seems to me that the motivation behind of ImageBaseColor is
> > to provide an efficient way to represent strips of constant
> > color. Of course we want it to be simple and practical too --
> > which I think the present definition is not. 
> > 
> > I propose that that the photometry and interpretation of the
> > ImageBaseColor field data be changed to be IDENTICAL TO that of
> > the containing IFD (including all applicable fields which
> > modify the representation and photometric interpretation of
> > color sample data). This means that the representation of
> > ImageBaseColor sample data would be identical to the
> > representation of the ordinary color sample data that it
> > represents (stands in place of). This would be extremely simple
> > and convenient, both for the creator of a TIFF data stream and
> > for the reader of a TIFF data stream! There would be NO
> > difference in the treatment of ordinary color sample data and
> > the color sample data in the ImageBaseColor field. 
> > 
> > 
> >     Dale Knutsen


-- 



    Dale Knutsen


_______________________________________________
Get your free email from http://webmail.earthlink.net



From owner-ietf-fax@mail.imc.org  Thu Aug  2 10:42:00 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA29564
	for <fax-archive@odin.ietf.org>; Thu, 2 Aug 2001 10:41:59 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f72DiAl10718
	for ietf-fax-bks; Thu, 2 Aug 2001 06:44:10 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f72Di7s10714
	for <ietf-fax@imc.org>; Thu, 2 Aug 2001 06:44:07 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id WAA06902;
	Thu, 2 Aug 2001 22:42:54 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id ABA97843;
	Thu, 2 Aug 2001 22:42:53 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id WAA29239; Thu, 2 Aug 2001 22:42:47 +0900
To: maeda@crf.canon.fr
Cc: Claudio.Allocchio@garr.it, ietf-fax@imc.org
Subject: Re: Absence of fax-wg at London
In-Reply-To: <3B691677.D0193B28@crf.canon.fr>
References: <3B691677.D0193B28@crf.canon.fr>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010802224607L.tamura@toda.ricoh.co.jp>
Date: Thu, 02 Aug 2001 22:46:07 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 35
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


MAEDA-san,

> I am very sorry that I can not attend the fax-wg at London on 6 August.
> We can discuss about drafts on the mailing list.
> 
> 5.3 Terminal mode issue                     30 min       98
> - draft-ietf-fax-terminal-mode-goals-00.txt
> - draft-ietf-fax-terminal-mode-protocol-00.txt
> - draft-ietf-fax-faxprocessing-status-00.txt

According to the current milestone,

  Jul 2001	Submit second draft of Fax status information

  Jul 2001	Submit second draft of Goal for Terminal Mode

  Jul 2001	Submit second draft of Protocol for Terminal Mode

  Dec 2001	Submit final draft of Fax status information

  Dec 2001	Submit final draft of Goal for Terminal Mode

  Dec 2001	Submit Final draft of Protocol for Terminal Mode

No second draft is done.
We should confirm your plan. Please let us know soon.

In my personal feeling, to make the target date late is not so good.


Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Thu Aug  2 14:44:10 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12448
	for <fax-archive@odin.ietf.org>; Thu, 2 Aug 2001 14:44:08 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f72Hqhi23341
	for ietf-fax-bks; Thu, 2 Aug 2001 10:52:43 -0700 (PDT)
Received: from zcars0m9.ca.nortel.com ([47.129.242.157])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f72Hqfs23337
	for <ietf-fax@imc.org>; Thu, 2 Aug 2001 10:52:42 -0700 (PDT)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.ca.nortel.com (8.11.0/8.11.0) with ESMTP id f72HnP925961
	for <ietf-fax@imc.org>; Thu, 2 Aug 2001 13:49:25 -0400 (EDT)
Received: from zcard015.ca.nortel.com by zcars04f.ca.nortel.com;
          Thu, 2 Aug 2001 13:49:29 -0400
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) 
          id <PMVSGBPB>; Thu, 2 Aug 2001 13:49:32 -0400
Message-ID: <D38D073716F2D411BEE400508BCF6296018A0B6C@zcard04k.ca.nortel.com>
From: "Glenn Parsons" <gparsons@nortelnetworks.com>
To: IETF Internet Fax WG <ietf-fax@imc.org>, Dan Wing <dwing@cisco.com>
Cc: Conrad Price <cprice@cisco.com>
Subject: RE: NSF values
Date: Thu, 2 Aug 2001 13:49:35 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C11B7B.7E3B7E00"
X-Orig: <gparsons@americasm01.nt.com>
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C11B7B.7E3B7E00
Content-Type: text/plain

Dan,  I believe TIA TR29 maintains the list for the US

Glenn.

> ----------
> From: 	Dan Wing
> Sent: 	Thursday, August 2, 2001 4:38 am
> To: 	IETF Internet Fax WG
> Cc: 	Conrad Price
> Subject: 	NSF values
> 
> 
> Anyone know of a canonical list -- other than T.35 -- which lists 
> NSF values assigned to each fax manufacturer?
> 
> -d
> 
> 
> 
> 

------_=_NextPart_001_01C11B7B.7E3B7E00
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.89">
<TITLE>RE: NSF values</TITLE>
</HEAD>
<BODY>

<P><FONT COLOR="#0000FF" FACE="Arial">Dan,&nbsp; I believe TIA TR29 maintains the list for the US</FONT>
</P>

<P><FONT COLOR="#0000FF" FACE="Arial">Glenn.</FONT>
</P>
<UL>
<P><FONT SIZE=2 FACE="Geneva">----------</FONT>
<BR><B><FONT SIZE=2 FACE="Geneva">From:</FONT></B> &nbsp; <FONT SIZE=2 FACE="Geneva">Dan Wing</FONT>
<BR><B><FONT SIZE=2 FACE="Geneva">Sent:</FONT></B> &nbsp; <FONT SIZE=2 FACE="Geneva">Thursday, August 2, 2001 4:38 am</FONT>
<BR><B><FONT SIZE=2 FACE="Geneva">To:</FONT></B> &nbsp;&nbsp;&nbsp; <FONT SIZE=2 FACE="Geneva">IETF Internet Fax WG</FONT>
<BR><B><FONT SIZE=2 FACE="Geneva">Cc:</FONT></B> &nbsp;&nbsp;&nbsp; <FONT SIZE=2 FACE="Geneva">Conrad Price</FONT>
<BR><B><FONT SIZE=2 FACE="Geneva">Subject:</FONT></B> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=2 FACE="Geneva">NSF values</FONT>
</P>
<BR>

<P><FONT SIZE=2 FACE="Monaco">Anyone know of a canonical list -- other than T.35 -- which lists </FONT>
<BR><FONT SIZE=2 FACE="Monaco">NSF values assigned to each fax manufacturer?</FONT>
</P>

<P><FONT SIZE=2 FACE="Monaco">-d</FONT>
</P>
<BR>
<BR>
<BR>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C11B7B.7E3B7E00--


From owner-ietf-fax@mail.imc.org  Thu Aug  2 22:55:42 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA14232
	for <fax-archive@odin.ietf.org>; Thu, 2 Aug 2001 22:55:41 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f732B8V04510
	for ietf-fax-bks; Thu, 2 Aug 2001 19:11:08 -0700 (PDT)
Received: from postoffice.sarnoff.com (postoffice.sarnoff.com [130.33.10.147])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f732B6s04503
	for <ietf-fax@imc.org>; Thu, 2 Aug 2001 19:11:06 -0700 (PDT)
Received: from postoffice.sarnoff.com ([127.0.0.1]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          SMTP id GHGYL000.NDJ for <ietf-fax@imc.org>; Thu, 2 Aug 2001
          21:53:25 -0400 
Received: from nova.sarnoff.com ([130.33.8.27]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          ESMTP id GH5ELU00.54I; Fri, 27 Jul 2001 16:08:18 -0400 
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by nova.sarnoff.com (8.9.2/8.9.2) with ESMTP id TAA06703;
	Thu, 26 Jul 2001 19:27:09 -0400 (EDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA11690
	for ietf-123-outbound.05@ietf.org; Thu, 26 Jul 2001 18:55:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA11669
	for <all-ietf@loki.ietf.org>; Thu, 26 Jul 2001 18:49:22 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19279;
	Thu, 26 Jul 2001 18:49:18 -0400 (EDT)
Message-Id: <200107262249.SAA19279@ietf.org>
To: IETF-Announce: ;
Cc: ietf-fax@imc.org
From: The IESG <iesg-secretary@ietf.org>
SUBJECT: Last Call: Implementers Guide for Facsimile Using Internet
	 Mail to Informational
Reply-to: iesg@ietf.org
Date: Thu, 26 Jul 2001 18:49:18 -0400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>



The IESG has received a request from the Internet Fax Working Group to
consider Implementers Guide for Facsimile Using Internet Mail
<draft-ietf-fax-implementers-guide-07.txt> as an Informational RFC.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by August 26, 2001.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-fax-implementers-guide-07.txt



From owner-ietf-fax@mail.imc.org  Fri Aug  3 05:30:37 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA10951
	for <fax-archive@odin.ietf.org>; Fri, 3 Aug 2001 05:30:36 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f738sui05090
	for ietf-fax-bks; Fri, 3 Aug 2001 01:54:56 -0700 (PDT)
Received: from postoffice.sarnoff.com (postoffice.sarnoff.com [130.33.10.147])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f738sss05078
	for <ietf-fax@imc.org>; Fri, 3 Aug 2001 01:54:54 -0700 (PDT)
Received: from postoffice.sarnoff.com ([127.0.0.1]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          SMTP id GHHF5H00.7PZ for <ietf-fax@imc.org>; Fri, 3 Aug 2001
          03:51:17 -0400 
Received: from nova.sarnoff.com ([130.33.8.27]) by
          postoffice.sarnoff.com (Netscape Messaging Server 4.15) with
          ESMTP id GH5ELU00.54I; Fri, 27 Jul 2001 16:08:18 -0400 
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by nova.sarnoff.com (8.9.2/8.9.2) with ESMTP id TAA06703;
	Thu, 26 Jul 2001 19:27:09 -0400 (EDT)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA11690
	for ietf-123-outbound.05@ietf.org; Thu, 26 Jul 2001 18:55:00 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA11669
	for <all-ietf@loki.ietf.org>; Thu, 26 Jul 2001 18:49:22 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19279;
	Thu, 26 Jul 2001 18:49:18 -0400 (EDT)
Message-Id: <200107262249.SAA19279@ietf.org>
To: IETF-Announce: ;
Cc: ietf-fax@imc.org
From: The IESG <iesg-secretary@ietf.org>
SUBJECT: Last Call: Implementers Guide for Facsimile Using Internet
	 Mail to Informational
Reply-to: iesg@ietf.org
Date: Thu, 26 Jul 2001 18:49:18 -0400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>



The IESG has received a request from the Internet Fax Working Group to
consider Implementers Guide for Facsimile Using Internet Mail
<draft-ietf-fax-implementers-guide-07.txt> as an Informational RFC.

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by August 26, 2001.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-fax-implementers-guide-07.txt



From owner-ietf-fax@mail.imc.org  Fri Aug  3 06:31:18 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA12335
	for <fax-archive@odin.ietf.org>; Fri, 3 Aug 2001 06:31:17 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f739wbv08190
	for ietf-fax-bks; Fri, 3 Aug 2001 02:58:37 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f739wZs08179
	for <ietf-fax@imc.org>; Fri, 3 Aug 2001 02:58:35 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id SAA17875
	for <ietf-fax@imc.org>; Fri, 3 Aug 2001 18:58:35 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id ABB16874;
	Fri, 3 Aug 2001 18:58:34 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id SAA08632 for <ietf-fax@imc.org>; Fri, 3 Aug 2001 18:58:27 +0900
To: ietf-fax@imc.org
Subject: Your slides at London meeting
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010803190148E.tamura@toda.ricoh.co.jp>
Date: Fri, 03 Aug 2001 19:01:48 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 16
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


To those who make a presesetation at IETF-FAX meeting at London.

If possible, please send your powerpoint or pdf file that you use
in our session to Claudio and me before our meeting starts.

If we could collect all slides beforehand, we can save our time
to change the personal computer.

Either mail to us or direct hand-over is ok, even on Monday.

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp




From owner-ietf-fax@mail.imc.org  Fri Aug  3 08:35:00 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA14552
	for <fax-archive@odin.ietf.org>; Fri, 3 Aug 2001 08:34:59 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f73Bj4q13759
	for ietf-fax-bks; Fri, 3 Aug 2001 04:45:04 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f73Bj2s13755
	for <ietf-fax@imc.org>; Fri, 3 Aug 2001 04:45:02 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id UAA20342
	for <ietf-fax@imc.org>; Fri, 3 Aug 2001 20:45:02 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id ABB18740;
	Fri, 3 Aug 2001 20:44:56 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id UAA09557 for <ietf-fax@imc.org>; Fri, 3 Aug 2001 20:44:49 +0900
To: ietf-fax@imc.org
Subject: Re: Your slides at London meeting
In-Reply-To: <20010803190148E.tamura@toda.ricoh.co.jp>
References: <20010803190148E.tamura@toda.ricoh.co.jp>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010803204810J.tamura@toda.ricoh.co.jp>
Date: Fri, 03 Aug 2001 20:48:10 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 25
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Also, 

Please clarify your target date for our milestone.

From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
Subject: Your slides at London meeting
Date: Fri, 03 Aug 2001 19:01:48 +0900 (JST)

> 
> To those who make a presesetation at IETF-FAX meeting at London.
> 
> If possible, please send your powerpoint or pdf file that you use
> in our session to Claudio and me before our meeting starts.
> 
> If we could collect all slides beforehand, we can save our time
> to change the personal computer.
> 
> Either mail to us or direct hand-over is ok, even on Monday.
> 
> Regards,
> --
> Hiroshi Tamura, Co-chair of IETF-FAX WG
> E-mail: tamura@toda.ricoh.co.jp
> 
> 


From owner-ietf-fax@mail.imc.org  Fri Aug  3 10:36:16 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA16951
	for <fax-archive@odin.ietf.org>; Fri, 3 Aug 2001 10:36:15 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f73DxCh16065
	for ietf-fax-bks; Fri, 3 Aug 2001 06:59:12 -0700 (PDT)
Received: from salvelinus.brooktrout.com (salvelinus.brooktrout.com [204.176.205.6])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f73DxAs16061
	for <ietf-fax@imc.org>; Fri, 3 Aug 2001 06:59:11 -0700 (PDT)
Received: from nhmail1.admin.brooktrout.com (nhmail1.admin.brooktrout.com [204.176.75.8])
	by salvelinus.brooktrout.com (8.9.3/8.9.3) with ESMTP id JAA13436;
	Fri, 3 Aug 2001 09:46:22 -0400 (EDT)
Received: by nhmail1.admin.brooktrout.com with Internet Mail Service (5.5.2653.19)
	id <P74S6YRV>; Fri, 3 Aug 2001 09:49:42 -0400
Message-ID: <11740AB18BD4D111BE8F00A0C9B8044F05529D9C@nhmail1.admin.brooktrout.com>
From: James Rafferty <jraff@brooktrout.com>
To: "'Glenn Parsons'" <gparsons@nortelnetworks.com>,
        IETF Internet Fax WG
	 <ietf-fax@imc.org>, Dan Wing <dwing@cisco.com>
Cc: "Jim Dahmen (E-mail)" <jdahmen@atl.mediaone.net>
Subject: RE: NSF values
Date: Fri, 3 Aug 2001 09:49:41 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C11C23.25288490"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C11C23.25288490
Content-Type: text/plain;
	charset="iso-8859-1"

Well, TR-29 has now become TR30.5 and Jim Dahmen is chair.  
 
You could check with him.  Steve Urban of Delta Information Systems (former
TR-29 chair) had been doing it, but
I'm not sure if he passed it on to the committee or not.     
 
James

-----Original Message-----
From: Glenn Parsons [mailto:gparsons@nortelnetworks.com]
Sent: Thursday, August 02, 2001 1:50 PM
To: IETF Internet Fax WG; Dan Wing
Cc: Conrad Price
Subject: RE: NSF values



Dan,  I believe TIA TR29 maintains the list for the US 

Glenn. 

	---------- 
From:   Dan Wing 
Sent:   Thursday, August 2, 2001 4:38 am 
To:     IETF Internet Fax WG 
Cc:     Conrad Price 
Subject:        NSF values 


	Anyone know of a canonical list -- other than T.35 -- which lists 
NSF values assigned to each fax manufacturer? 

	-d 





------_=_NextPart_001_01C11C23.25288490
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: NSF values</TITLE>

<META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=160264013-03082001><FONT face=Arial color=#0000ff size=2>Well, 
TR-29 has now become TR30.5 and Jim Dahmen is chair.&nbsp; </FONT></SPAN></DIV>
<DIV><SPAN class=160264013-03082001><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=160264013-03082001><FONT face=Arial color=#0000ff size=2>You 
could check with him.&nbsp;&nbsp;Steve Urban of Delta Information Systems 
(former TR-29 chair) had been doing it, but</FONT></SPAN></DIV>
<DIV><SPAN class=160264013-03082001><FONT face=Arial color=#0000ff size=2>I'm 
not sure if he passed it on to the committee or not.&nbsp;&nbsp; &nbsp; 
</FONT></SPAN></DIV>
<DIV><SPAN class=160264013-03082001><FONT face=Arial color=#0000ff 
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=160264013-03082001><FONT face=Arial color=#0000ff 
size=2>James</FONT></SPAN></DIV>
<BLOCKQUOTE 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> Glenn Parsons 
  [mailto:gparsons@nortelnetworks.com]<BR><B>Sent:</B> Thursday, August 02, 2001 
  1:50 PM<BR><B>To:</B> IETF Internet Fax WG; Dan Wing<BR><B>Cc:</B> Conrad 
  Price<BR><B>Subject:</B> RE: NSF values<BR><BR></FONT></DIV>
  <P><FONT face=Arial color=#0000ff>Dan,&nbsp; I believe TIA TR29 maintains the 
  list for the US</FONT> </P>
  <P><FONT face=Arial color=#0000ff>Glenn.</FONT> </P>
  <UL>
    <P><FONT face=Geneva size=2>----------</FONT> <BR><B><FONT face=Geneva 
    size=2>From:</FONT></B> &nbsp; <FONT face=Geneva size=2>Dan Wing</FONT> 
    <BR><B><FONT face=Geneva size=2>Sent:</FONT></B> &nbsp; <FONT face=Geneva 
    size=2>Thursday, August 2, 2001 4:38 am</FONT> <BR><B><FONT face=Geneva 
    size=2>To:</FONT></B> &nbsp;&nbsp;&nbsp; <FONT face=Geneva size=2>IETF 
    Internet Fax WG</FONT> <BR><B><FONT face=Geneva size=2>Cc:</FONT></B> 
    &nbsp;&nbsp;&nbsp; <FONT face=Geneva size=2>Conrad Price</FONT> <BR><B><FONT 
    face=Geneva size=2>Subject:</FONT></B> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
    <FONT face=Geneva size=2>NSF values</FONT> </P><BR>
    <P><FONT face=Monaco size=2>Anyone know of a canonical list -- other than 
    T.35 -- which lists </FONT><BR><FONT face=Monaco size=2>NSF values assigned 
    to each fax manufacturer?</FONT> </P>
    <P><FONT face=Monaco size=2>-d</FONT> 
</P><BR><BR><BR></UL></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C11C23.25288490--


From owner-ietf-fax@mail.imc.org  Fri Aug  3 12:07:16 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA19365
	for <fax-archive@odin.ietf.org>; Fri, 3 Aug 2001 12:07:15 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f73FTeZ19936
	for ietf-fax-bks; Fri, 3 Aug 2001 08:29:40 -0700 (PDT)
Received: from femail22.sdc1.sfba.home.com (femail22.sdc1.sfba.home.com [24.0.95.147])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f73FTcs19931
	for <ietf-fax@imc.org>; Fri, 3 Aug 2001 08:29:38 -0700 (PDT)
Received: from home.com ([24.3.205.203]) by femail22.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP
          id <20010803152920.PKXJ9561.femail22.sdc1.sfba.home.com@home.com>;
          Fri, 3 Aug 2001 08:29:20 -0700
Message-ID: <3B6AC39F.5A68F6B4@home.com>
Date: Fri, 03 Aug 2001 11:30:39 -0400
From: "Herman R. Silbiger" <hsilbiger@home.com>
Reply-To: hsilbiger@ieee.org
Organization: APPLICOM
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: James Rafferty <jraff@brooktrout.com>
CC: "'Glenn Parsons'" <gparsons@nortelnetworks.com>,
        IETF Internet Fax WG <ietf-fax@imc.org>, Dan Wing <dwing@cisco.com>,
        "Jim Dahmen (E-mail)" <jdahmen@atl.mediaone.net>
Subject: Re: NSF values
References: <11740AB18BD4D111BE8F00A0C9B8044F05529D9C@nhmail1.admin.brooktrout.com>
Content-Type: multipart/alternative;
 boundary="------------F1618ADBD43ABAA43EFFC90C"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>



--------------F1618ADBD43ABAA43EFFC90C
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I have the list as of 1995.

Herman

James Rafferty wrote:

>  Well, TR-29 has now become TR30.5 and Jim Dahmen is chair. You could
> check with him.  Steve Urban of Delta Information Systems (former
> TR-29 chair) had been doing it, butI'm not sure if he passed it on to
> the committee or not. James
>
>      -----Original Message-----
>      From: Glenn Parsons [mailto:gparsons@nortelnetworks.com]
>      Sent: Thursday, August 02, 2001 1:50 PM
>      To: IETF Internet Fax WG; Dan Wing
>      Cc: Conrad Price
>      Subject: RE: NSF values
>
>      Dan,  I believe TIA TR29 maintains the list for the US
>
>      Glenn.
>
>           ----------
>           From:   Dan Wing
>           Sent:   Thursday, August 2, 2001 4:38 am
>           To:     IETF Internet Fax WG
>           Cc:     Conrad Price
>           Subject:        NSF values
>
>           Anyone know of a canonical list -- other than T.35 --
>           which lists
>           NSF values assigned to each fax manufacturer?
>
>           -d
>
>
>

--------------F1618ADBD43ABAA43EFFC90C
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I have the list as of 1995.
<p>Herman
<p>James Rafferty wrote:
<blockquote TYPE=CITE>&nbsp;<span class=160264013-03082001><font face="Arial"><font color="#0000FF"><font size=-1>Well,
TR-29 has now become TR30.5 and Jim Dahmen is chair.&nbsp;</font></font></font></span><span class=160264013-03082001></span><span class=160264013-03082001><font face="Arial"><font color="#0000FF"><font size=-1>You
could check with him.&nbsp; Steve Urban of Delta Information Systems (former
TR-29 chair) had been doing it, but</font></font></font></span><span class=160264013-03082001><font face="Arial"><font color="#0000FF"><font size=-1>I'm
not sure if he passed it on to the committee or not.&nbsp;</font></font></font></span><span class=160264013-03082001></span><span class=160264013-03082001><font face="Arial"><font color="#0000FF"><font size=-1>James</font></font></font></span>
<blockquote 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid">
<div class="OutlookMessageHeader" dir="ltr"><font face="Tahoma"><font size=-1>-----Original
Message-----</font></font>
<br><font face="Tahoma"><font size=-1><b>From:</b> Glenn Parsons [<A HREF="mailto:gparsons@nortelnetworks.com">mailto:gparsons@nortelnetworks.com</A>]</font></font>
<br><font face="Tahoma"><font size=-1><b>Sent:</b> Thursday, August 02,
2001 1:50 PM</font></font>
<br><font face="Tahoma"><font size=-1><b>To:</b> IETF Internet Fax WG;
Dan Wing</font></font>
<br><font face="Tahoma"><font size=-1><b>Cc:</b> Conrad Price</font></font>
<br><font face="Tahoma"><font size=-1><b>Subject:</b> RE: NSF values</font></font>
<br>&nbsp;</div>
<font face="Arial"><font color="#0000FF">Dan,&nbsp; I believe TIA TR29
maintains the list for the US</font></font>
<p><font face="Arial"><font color="#0000FF">Glenn.</font></font>
<ul><font face="Geneva"><font size=-1>----------</font></font>
<br><b><font face="Geneva"><font size=-1>From:</font></font></b>&nbsp;&nbsp;
<font face="Geneva"><font size=-1>Dan Wing</font></font>
<br><b><font face="Geneva"><font size=-1>Sent:</font></font></b>&nbsp;&nbsp;
<font face="Geneva"><font size=-1>Thursday, August 2, 2001 4:38 am</font></font>
<br><b><font face="Geneva"><font size=-1>To:</font></font></b>&nbsp;&nbsp;&nbsp;&nbsp;
<font face="Geneva"><font size=-1>IETF Internet Fax WG</font></font>
<br><b><font face="Geneva"><font size=-1>Cc:</font></font></b>&nbsp;&nbsp;&nbsp;&nbsp;
<font face="Geneva"><font size=-1>Conrad Price</font></font>
<br><b><font face="Geneva"><font size=-1>Subject:</font></font></b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<font face="Geneva"><font size=-1>NSF values</font></font>
<p><font face="Monaco"><font size=-1>Anyone know of a canonical list --
other than T.35 -- which lists</font></font>
<br><font face="Monaco"><font size=-1>NSF values assigned to each fax manufacturer?</font></font>
<p><font face="Monaco"><font size=-1>-d</font></font>
<br>&nbsp;
<br>&nbsp;</ul>
</blockquote>
</blockquote>
</html>

--------------F1618ADBD43ABAA43EFFC90C--



From owner-ietf-fax@mail.imc.org  Fri Aug  3 22:58:18 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04547
	for <fax-archive@odin.ietf.org>; Fri, 3 Aug 2001 22:58:18 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f742EBN09642
	for ietf-fax-bks; Fri, 3 Aug 2001 19:14:11 -0700 (PDT)
Received: from jxmls04.se.mediaone.net (jxmls04.se.mediaone.net [24.129.0.51])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f742E8s09638
	for <ietf-fax@imc.org>; Fri, 3 Aug 2001 19:14:08 -0700 (PDT)
Received: from jdahmen (rr-163-50-18.atl.mediaone.net [24.163.50.18])
	by jxmls04.se.mediaone.net (8.11.1/8.11.1) with SMTP id f742CI500630;
	Fri, 3 Aug 2001 22:12:19 -0400 (EDT)
Reply-To: <jdahmen@atl.mediaone.net>
From: "Jim Dahmen" <jdahmen@atl.mediaone.net>
To: <hsilbiger@ieee.org>, "'James Rafferty'" <jraff@brooktrout.com>
Cc: "'Glenn Parsons'" <gparsons@nortelnetworks.com>,
        "'IETF Internet Fax WG'" <ietf-fax@imc.org>,
        "'Dan Wing'" <dwing@cisco.com>
Subject: RE: NSF values
Date: Fri, 3 Aug 2001 22:20:19 -0400
Message-ID: <002701c11c8c$0274e920$1232a318@atl.mediaone.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0028_01C11C6A.7B634920"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <3B6AC39F.5A68F6B4@home.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


This is a multi-part message in MIME format.

------=_NextPart_000_0028_01C11C6A.7B634920
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I have passed on the info that we have to Dan. I will check with Steve for
additions.

Best regards,
Jim

  -----Original Message-----
  From: Herman R. Silbiger [mailto:hsilbiger@home.com]
  Sent: Friday, August 03, 2001 11:31 AM
  To: James Rafferty
  Cc: 'Glenn Parsons'; IETF Internet Fax WG; Dan Wing; Jim Dahmen (E-mail)
  Subject: Re: NSF values


  I have the list as of 1995.
  Herman

  James Rafferty wrote:

     Well, TR-29 has now become TR30.5 and Jim Dahmen is chair. You could
check with him.  Steve Urban of Delta Information Systems (former TR-29
chair) had been doing it, butI'm not sure if he passed it on to the
committee or not. James
      -----Original Message-----
      From: Glenn Parsons [mailto:gparsons@nortelnetworks.com]
      Sent: Thursday, August 02, 2001 1:50 PM
      To: IETF Internet Fax WG; Dan Wing
      Cc: Conrad Price
      Subject: RE: NSF values

      Dan,  I believe TIA TR29 maintains the list for the US
      Glenn.

        ----------
        From:   Dan Wing
        Sent:   Thursday, August 2, 2001 4:38 am
        To:     IETF Internet Fax WG
        Cc:     Conrad Price
        Subject:        NSF values
        Anyone know of a canonical list -- other than T.35 -- which lists
        NSF values assigned to each fax manufacturer?

        -d




------=_NextPart_000_0028_01C11C6A.7B634920
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.50.4616.200" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D400191902-04082001><FONT face=3DArial color=3D#0000ff =
size=3D2>I have=20
passed on the info that we have to Dan. I will check with Steve for=20
additions.</FONT></SPAN></DIV>
<DIV>&nbsp;</DIV>
<P><FONT face=3DArial size=3D2>Best regards,</FONT> <BR><FONT =
face=3DArial=20
size=3D2>Jim</FONT> </P>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Herman R. Silbiger =

  [mailto:hsilbiger@home.com]<BR><B>Sent:</B> Friday, August 03, 2001 =
11:31=20
  AM<BR><B>To:</B> James Rafferty<BR><B>Cc:</B> 'Glenn Parsons'; IETF =
Internet=20
  Fax WG; Dan Wing; Jim Dahmen (E-mail)<BR><B>Subject:</B> Re: NSF=20
  values<BR><BR></FONT></DIV>I have the list as of 1995.=20
  <P>Herman=20
  <P>James Rafferty wrote:=20
  <BLOCKQUOTE TYPE=3D"CITE">&nbsp;<SPAN class=3D160264013-03082001><FONT =

    face=3DArial><FONT color=3D#0000ff><FONT size=3D-1>Well, TR-29 has =
now become=20
    TR30.5 and Jim Dahmen is =
chair.&nbsp;</FONT></FONT></FONT></SPAN><SPAN=20
    class=3D160264013-03082001></SPAN><SPAN =
class=3D160264013-03082001><FONT=20
    face=3DArial><FONT color=3D#0000ff><FONT size=3D-1>You could check =
with him.&nbsp;=20
    Steve Urban of Delta Information Systems (former TR-29 chair) had =
been doing=20
    it, but</FONT></FONT></FONT></SPAN><SPAN =
class=3D160264013-03082001><FONT=20
    face=3DArial><FONT color=3D#0000ff><FONT size=3D-1>I'm not sure if =
he passed it on=20
    to the committee or not.&nbsp;</FONT></FONT></FONT></SPAN><SPAN=20
    class=3D160264013-03082001></SPAN><SPAN =
class=3D160264013-03082001><FONT=20
    face=3DArial><FONT color=3D#0000ff><FONT=20
    size=3D-1>James</FONT></FONT></FONT></SPAN>=20
    <BLOCKQUOTE=20
    style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff =
2px solid">
      <DIV class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma><FONT=20
      size=3D-1>-----Original Message-----</FONT></FONT> <BR><FONT=20
      face=3DTahoma><FONT size=3D-1><B>From:</B> Glenn Parsons [<A=20
      =
href=3D"mailto:gparsons@nortelnetworks.com">mailto:gparsons@nortelnetwork=
s.com</A>]</FONT></FONT>=20
      <BR><FONT face=3DTahoma><FONT size=3D-1><B>Sent:</B> Thursday, =
August 02, 2001=20
      1:50 PM</FONT></FONT> <BR><FONT face=3DTahoma><FONT =
size=3D-1><B>To:</B> IETF=20
      Internet Fax WG; Dan Wing</FONT></FONT> <BR><FONT =
face=3DTahoma><FONT=20
      size=3D-1><B>Cc:</B> Conrad Price</FONT></FONT> <BR><FONT =
face=3DTahoma><FONT=20
      size=3D-1><B>Subject:</B> RE: NSF values</FONT></FONT> =
<BR>&nbsp;</DIV><FONT=20
      face=3DArial><FONT color=3D#0000ff>Dan,&nbsp; I believe TIA TR29 =
maintains the=20
      list for the US</FONT></FONT>=20
      <P><FONT face=3DArial><FONT color=3D#0000ff>Glenn.</FONT></FONT>=20
      <UL><FONT face=3DGeneva><FONT size=3D-1>----------</FONT></FONT>=20
        <BR><B><FONT face=3DGeneva><FONT=20
        size=3D-1>From:</FONT></FONT></B>&nbsp;&nbsp; <FONT =
face=3DGeneva><FONT=20
        size=3D-1>Dan Wing</FONT></FONT> <BR><B><FONT =
face=3DGeneva><FONT=20
        size=3D-1>Sent:</FONT></FONT></B>&nbsp;&nbsp; <FONT =
face=3DGeneva><FONT=20
        size=3D-1>Thursday, August 2, 2001 4:38 am</FONT></FONT> =
<BR><B><FONT=20
        face=3DGeneva><FONT =
size=3D-1>To:</FONT></FONT></B>&nbsp;&nbsp;&nbsp;&nbsp;=20
        <FONT face=3DGeneva><FONT size=3D-1>IETF Internet Fax =
WG</FONT></FONT>=20
        <BR><B><FONT face=3DGeneva><FONT=20
        size=3D-1>Cc:</FONT></FONT></B>&nbsp;&nbsp;&nbsp;&nbsp; <FONT=20
        face=3DGeneva><FONT size=3D-1>Conrad Price</FONT></FONT> =
<BR><B><FONT=20
        face=3DGeneva><FONT=20
        =
size=3D-1>Subject:</FONT></FONT></B>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;=20
        <FONT face=3DGeneva><FONT size=3D-1>NSF values</FONT></FONT>=20
        <P><FONT face=3DMonaco><FONT size=3D-1>Anyone know of a =
canonical list --=20
        other than T.35 -- which lists</FONT></FONT> <BR><FONT =
face=3DMonaco><FONT=20
        size=3D-1>NSF values assigned to each fax =
manufacturer?</FONT></FONT>=20
        <P><FONT face=3DMonaco><FONT size=3D-1>-d</FONT></FONT> =
<BR>&nbsp;=20
        =
<BR>&nbsp;</P></UL></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0028_01C11C6A.7B634920--



From owner-ietf-fax@mail.imc.org  Sat Aug  4 18:43:21 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01935
	for <fax-archive@odin.ietf.org>; Sat, 4 Aug 2001 18:43:21 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f74M2aR28039
	for ietf-fax-bks; Sat, 4 Aug 2001 15:02:36 -0700 (PDT)
Received: from lysithea.eastgw.xerox.com (lysithea.xerox.com [208.140.33.22])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f74M2Ls28033
	for <ietf-fax@imc.org>; Sat, 4 Aug 2001 15:02:21 -0700 (PDT)
Received: from godzilla.ADOC.xerox.com (godzilla.ADOC.xerox.com [13.242.128.10])
	by lysithea.eastgw.xerox.com (8.9.3/8.9.3) with ESMTP id SAA02053;
	Sat, 4 Aug 2001 18:02:09 -0400 (EDT)
Received: from mercury.adoc.xerox.com (mercury [13.242.100.20])
	by godzilla.ADOC.xerox.com (8.8.8+Sun/8.8.8/ADOC-HUB-1.7) with ESMTP id PAA18610;
	Sat, 4 Aug 2001 15:02:06 -0700 (PDT)
Received: by mercury.ADOC.xerox.com with Internet Mail Service (5.5.2653.19)
	id <PJRJ309J>; Sat, 4 Aug 2001 15:02:06 -0700
Message-ID: <51B8ABCE456FD111899900805F6FD6EE067A3503@mercury.ADOC.xerox.com>
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
To: "'Dale Knutsen'" <wdknutsen@earthlink.net>,
        "McIntyre, Lloyd"
	 <Lloyd.McIntyre@pahv.xerox.com>
Cc: "'IETF fax WG'" <ietf-fax@imc.org>,
        "'William Rucklidge 1'"
	 <wjr@imarkets.com>,
        "'Tim Platt'" <tp@scansoft.com>
Subject: RE: TIFF-FX  ImageBaseColor's photometry
Date: Sat, 4 Aug 2001 15:02:03 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


Dale,
We have reconsidered and accepted your latest proposal to use a new field in
accommodating use of the image color encoding parameters rather than only
ITULAB in the interpretation of ImageBaseColor. 

Our decision was base on:
1. Since there is currently no mechanism to enable ICC profiles in TIFF-FX,
your concern for the impact of profiles doesn't currently come into play.
However, we'd like to make sure that we don't preclude it's future use.

2. In the current use of TIFF-FX, if ICC profiles *were* used, then it would
likely be in one of two situations:
  a. A closed environment, where an input device is preparing a file for a
known output device.  In this case, both devices not only need to know how
to deal with ICC profiles, but they should make sure that they enable the
full use of the profiles.  In this case, we believe the reader and writer
should have full access to algorithms that can apply the profiles.  The end
result is that profiles shouldn't be an inhibitor.
  b. An open environment.  In this case the preference might be to maintain
a device-independent color space.  Otherwise, the profiles ought to be dealt
with correctly, and ought to be well understood (algorithms available).

3. In the remote but likely case that someone gets a file with the image
data coupled to an ICC profile, and the ImageBaseColor is not, there's the
risk that the image data will contrast with the "default color" of the
ImageBaseColor, notably when compared to the original.  The contrast is
relative, such that if the default and image data had the same wrong ICC
profile applied, the contrast should not stand out.  However, with the
current ImageBaseColor approach, the image color will be perceptibly
different from that of the adjoining color derived from the ImageBaseColor -
this becomes the most important factor.

Given the expectation that ICC profiles may one day work themselves into
TIFF-FX, we feel it prudent to make provisions in the use of ImageBaseColor
for consistent color data.  We are proposing the following new field, to be
used in place of ImageBaseColor, when using TIFF-FX extensions (any file
containing the TIFF-FXExtension field).

The new field, IFDBaseColor, is defined within a new subsection "E1.2.1.3.2
New fields required for designated profiles" as below.

Regards,
Lloyd

E1.2.1.3.2 New fields required for designated profiles

IFDBaseColor Field
   This field applies to Profiles M and T, however it is only
   recommended for Profile T. The IFDBaseColor field is introduced as a
   duplication of ImageBaseColor, which is tied to the ITU L*a*b* color
   space, as a way to keep the color space of the image data in sync
   with that of the 0-byte strips.  This should not be a significant
   factor when device-independent color data is present, but may be a
   factor should device-dependent image data be considered, coupled with
   the device-independent color value stored in ImageBaseColor.  More
   notably, if ICC Profiles were to be used, it is possible that
   misinterpretation of the image data may cause the ImageBaseColor to
   contrast.  Keeping the color interpretation in sync would avoid
   possible contrasting.  Furthermore, color space conversion
   differences to and from ITU L*a*b* and the intended color space could
   be avoided.

   In keeping with the constraint that this extension set requires no
   modification of existing TIFF-FX implementations, this field SHALL be
   used only when the TIFF-FXExtensions field is present, and SHOULD
   exist along with the ImageBaseColor field. When both fields are
   present, the IFDBaseColor field takes precedence, and it's at the
   discretion of the writer to determine the color values that will go
   into the ImageBaseColor, knowing that a base TIFF-FX reader will see
   only the ImageBaseColor. If extensions are used to the point that a
   base TIFF-FX reader may not be able to reasonably read the image
   anyway, the ImageBaseColor MAY be omitted.

IFDBaseColor(34700).                                       CHAR or SHORT
   Count = SamplesPerPixel
   In areas of an image layer where no image data is available (i.e.
   where no strips are defined, or where the StripByteCounts entry for a
   given strip is 0), the color specified by IFDBaseColor SHALL be used,
   and SHOULD exist along with the ImageBaseColor field.  This field is
   used in a similar manner to ImageBaseColor, but is tied to the color
   characteristics of the IFD, not ITU L*a*b*.

   The color specified by IFDBaseColor SHALL be described by the color
   characteristics of the IFD: PhotometricInterpretation,
   SamplesPerPixel, BitsPerSample and, depending on the value of
   PhotometricInterpretation, all other fields of the IFD that affect
   the interpretation of color samples. For example, if the
   PhotometricInterpretation is ITU L*A*B*, then the color is further
   described by the gamut defined in the Decode field, if any, and by
   the Indexed field where applicable. This insures that the
   IFDBaseColor is represented in exactly the same way as any image
   data that is represented.

   Note that there is currently no provision for color profile data in
   TIFF-FX.

   Each color component may be stored in a CHAR array, if BitsPerSample
   is 8 or less.  If BitsPerSample is less than that of the IFDBaseColor
   array element (8 for CHAR and 16 for SHORT), then the 'BitsPerSample'
   least-significant bits are used to hold the color component(s).  For
   example, if BitsPerSample is 4, then the lower 4 bits in each CHAR or
   SHORT will hold the color components.

   Other than color designation, IFDBaseColor is used as described by
   ImageBaseColor.
   To define a child IFD specifying a IFDBaseColor but containing no
   encoded image data, create an IFD with PhotometricInterpretation,
   SamplesPerPixel, BitsPerSample and any other field(s) required to
   specify color Characteristics. The IFD will also contain the
   following settings.

      ImageLayer[0]:             specified layer
      ImageLayer[1]:             less than any other IFDs corresponding
                                 to the same layer and strip.
      RowsPerStrip:              strip height
      ImageLength:               strip height
      ImageWidth:                full image width
      Compression:               1 (none)
      X/YResolution:             that of the Primary IFD
      XPosition:                 0
      YPosition:                 the offset from the top of the page to
                                 the beginning of the strip in the 
                                 resolution units of inches
      StripByteCounts:           single 0 value
      StripOffsets:              single 0 entry
      NewSubFileType:            bit 4 set   (MRC)
      ImageBaseColor:            desired color

   For the Foreground layer image(s), the default value for the
   IFDBaseColor field is black. For other cases, including the
   Background layer image, the default value is white.

> -----Original Message-----
> From: Dale Knutsen [mailto:wdknutsen@earthlink.net]
> Sent: Thursday, August 02, 2001 5:24 AM
> To: Lloyd.McIntyre@pahv.xerox.com; wdknutsen@earthlink.net
> Cc: 'IETF fax WG'
> Subject: RE: TIFF-FX ImageBaseColor's photometry
> 
> 
> Lloyd,
> 
> Thanks for your thoughtful reply. I understand the
> requirement for backward compatibility. And in that light I
> offer the following proposal, which might be found to meet
> all concerns.
> 
> In TIFF-FX Extension Set 1, define a new field, I'll call it
> NewImageBaseColor, that is the same as ImageBaseColor except
> that the photometry and interpretation of the
> NewImageBaseColor field data is specified to be identical to
> that of the containing IFD (including all applicable fields
> which modify the representation and photometric
> interpretation of color sample data).
> 
> For a writer of a TIFF-FX Extension Set 1 data set who
> wishes to use NewImageBaseColor, to conform to the base
> TIFF-FX standard the writer will include the standard
> ImageBaseColor field as well as the NewImageBaseColor field.
> This is no benefit to the writer, but it is extremely simple
> and easy to do, and so adds negligible costs to the writer.
> 
> The benefit of the proposed change accrues to the reader of a
> TIFF-FX Extension Set 1 data set, who may use the following
> algorithm when dealing with a strip that has a strip byte
> count of zero:
> 
>    IF NewImageBaseColor is present, then use its content to
>    render the color in the color space of the image of which
>    the strip is a part. This is simple, accurate, and very
>    efficient.
> 
>    ELSE Use the ImageBaseColor field. If the color space of
>    the image of which the strip is a part has photometry
>    other than ITULAB, the reader must convert the
>    ImageBaseColor data to the required output photometry.
> 
> 
> As you know, I claim that this conversion (of ITULAB to an
> arbitrary photometry) is onerous and problematical in many
> system environments. Nevertheless, the addition of
> NewImageBaseColor provides to readers of a TIFF-FX Extension
> Set 1 data set an efficient, accurate, and simple way of
> rendering fill colors in cases where the writer has utilized
> NewImageBaseColor, while at the same time not significantly
> increasing the complexity of software required to support
> both TIFF-FX Extension Set 1 as well as the base TIFF-FX
> standard.
> 
>     Dale Knutsen


From owner-ietf-fax@mail.imc.org  Wed Aug  8 02:29:07 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06733
	for <fax-archive@odin.ietf.org>; Wed, 8 Aug 2001 02:29:07 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f785ZFY25771
	for ietf-fax-bks; Tue, 7 Aug 2001 22:35:15 -0700 (PDT)
Received: from pp-mx0.tokyo.spin.ad.jp (PP-mx0.Tokyo.Spin.AD.JP [165.76.52.9])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f785ZDN25767
	for <ietf-fax@imc.org>; Tue, 7 Aug 2001 22:35:13 -0700 (PDT)
Received: from localhost (host217-33-138-213.ietf.ignite.net [217.33.138.213]) by pp-mx0.tokyo.spin.ad.jp (8.8.8+Spin/3.6W-JENS-stand2(09/30/00)) id OAA20061; Wed, 8 Aug 2001 14:35:04 +0900 (JST)
To: ietf-fax@imc.org
Subject: test, please ignore
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010808143546Q.adm@ifax.attnet.ne.jp>
Date: Wed, 08 Aug 2001 14:35:46 +0900 (JST)
X-Dispatcher: imput version 20000228(IM140)
Lines: 2
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


test, please ignoore.



From owner-ietf-fax@mail.imc.org  Thu Aug  9 12:13:38 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28958
	for <fax-archive@odin.ietf.org>; Thu, 9 Aug 2001 12:13:37 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f79FQuP21148
	for ietf-fax-bks; Thu, 9 Aug 2001 08:26:56 -0700 (PDT)
Received: from elettra.trieste.it (SYNX02.elettra.trieste.it [140.105.2.2])
	by above.proper.com (8.11.3/8.11.3) with SMTP id f79FQrN21142
	for <ietf-fax@imc.org>; Thu, 9 Aug 2001 08:26:53 -0700 (PDT)
Date: Thu, 9 Aug 2001 17:26:16 +0100
To: ietf-fax@imc.org
cc: klensin@jck.com
Message-ID: <Pine.VMS.3.91-B.1010809170453.46409A-100000@SYNX02.elettra.trieste.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
Subject: notes from the ietf FAX wg meeting at IETF 51
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by above.proper.com id f79FQtN21143
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit



Hallo, 

here are the notes from the meeting we had on monday evening.  Sorry for
being late, but (apart from an "editing accident" which deleted the first
version of the notes) I tried to be as most precise as possible, as some
issues are very important to be understood also on the mailing list by
those who were not present at the meeting. 

Please drop comments and integrations to our ML. Thanks again o Graham 
Klyne who took the base notes.

Regards
Claudio Allocchio
----------------------------------


Short notes of the ietf FAX WG meeting - IETF 51 London, UK
------------------------------------------------------

At the meeting start the co-chair welcomed the participants, and asked for
eventual modifications to the proposed agenda. As ther were no specific
change requests, the agenda was approved. 

Tamura-san announced that Maeda-san was unfortunaely not present at the
meeting, thus we would add more time to the discussion of the TIFF issues. 

2. Status of Draft Standard consideration
  2.1 Addressing
       draft-ietf-fax-minaddr-v2-04.txt
       draft-ietf-fax-faxaddr-v2-04.txt

These two documents were approved by IESG on July 19th 2001 and now are in
the RFC editor queue for publication. In the Applications Open Area
meeting there was the suggestion to find a way to explicitly state that
the specification draft-ietf-fax-minaddr-v2-04.txt is a general
specification which is valid in ANY application encoding GSTN (telephone)
numbers into an e-mail address.  Also the FAX wg suggested to add such
note, possibly in the abstract. The editor will investigate with the ADs
if an IESG note in appropriate. 

The same need to emphasize the generality could apply also to other FAX wg
documents, like the draft-ietf-fax-content-negotiation-05.txt ones and the
wg suggested the editors to consider it, too. 

 2.2 TIFF-FX
      draft-ietf-fax-tiff-fx-09.txt
      draft-ietf-fax-tiff-regbis-02.txt

The documents approval is slowed down by a series of problems which were
detected during the process. ITU-T also needs a quick resolution of there
problems as stated in the communication letter from ITU-T SG16 meeting.

The problem, detected at first as an IPR issue raised by Adobe in January 
2001, was escalated to IESG and IAB which examined carefully all the aspects,
and identified also some additional compatibility issues. 

John Klensin (IAB) reported to the WG.

The TIFF Story, actually had many different steps and chapters. During the
analysis of the problem there were many iterations between the IESG and
the IAB which at the end pointed out two Separate Issues: 

 - WG responsibility for interoperability
 - IPR questions

At first the interoperability. This is the "Main IETF Goal" to be
achieved, and its meaning should span forward and sideways. The main
principles are that: 

 - Implementations of one protocol must interoperate
Ð- Implementations of related protocols should interoperate
Ð- Deviations must make sense and have a clear rationale behind.

In its original goals (and as stated in the charter) the fax wg had to
create a Fax Model that should Interoperate with fax fabric and
Interoperate with e-mail fabric. More over it should avoid having to
choose between the two fabrics. For this reason TIFF was chosen because It
was widely believed that it would be interoperable with existing viewers
and editors, especially Viewers expected to be used with image/tiff in
e-mail. This shoud also be the start of the "global messaging service". 

The question now is: can we meet all these constrains? Is TIFF the right
choice to accomplish them? 

Basic TIFF does not support colors, and different resolutions, but is it
compliant with the existing TIFF readers, and e-mail User Agents (MUAs).
However, if we want to cover also the "extensions" that ITU-T is
requesting for fax service (e.g. colors, resolutions, etc...) Basic TIFF
is not enough, and it will need extensions. These extensions were
specified into TIFF-FX, and ITU-T decided to adopt and reference it.
However TIFF-FX is already beyond Basic TIFF. 

Actually there are already de facto extensions to basic TIFF
specifications which are publicly available, and widely deployed within
both TIFF readers and MUAs. All there de facto extensions are currently
used in MIME type "image/tiff" and there are not interoperability
problems. However the extensions intriduced into TIFF-FX are a superset,
and thus only some Ifax devices can correctly handle them. 

So, the IESG and IAB would like the WG to review and document, as a condition
for advancing the TIFF specification to Draft Standard:

 - Whether the choice of "interoperation with e-mail" versus "interoperation
   with fax" is the right one
 - whether a mostly-fax-only TIFF variation is the right choice
 - Whether this should be image/tiff or image/tifffx (or equivalent)
 - hether the interoperability profile is right given these issues
 - and any other similar tradeoffs that might have been made without full
   evaluation.

The IAB believes now it is late in the game, so these reviews may not
change anything, but they are important for learning, and context, and
predicting problem areas and determining whether the meta-qualifications
for Draft Standard are met. 

John Klensin then reported on the IPR issues, which invove both Adobe and 
Xerox.

Adobe:  the solution appears to be to have Adobe include the new TIFF-FX
encodings in TIFF-7, but Adobe has not committed to produce TIFF-7 and It
is not clear what produces that commitment. Moreover, even if they do
TIFF-7, they will not commit to including the TIFF-FX features until at
least Xerox releases rights to the encoding techniques for all uses of
TIFF, not just fax and Xerox (or maybe IETF) apply formally to Adobe to
have the features and tags included. At last, but not the least, no one at
this IETF can commit Adobe. 

Xerox: Xerox is willing to release rights for all uses in TIFF if Adobe
will adopt them and include them in TIFF-7. But no one here can commit
Xerox either. 

Thus it seems a viable solution currently in a deadlock waiting for
somebody to make the first move. 

At last, we have the ITU issue, who is referencing our documents. But ITU
approach to IPR is different, and a licence issued to the IETF might not
fully apply also to ITU. There is a strict need to coordinate with ITU
also on these IPR matters, to avoid future problems. It is in fact clear
that what was released to IETF is not automatically released to ITU (and
viceversa). 

The discussion of the problem and the WG conclusions.
-------------------------------------------------

The original reasons for using TIFF were lightweight, extensibility and
its ITU compatibility, and it ability to be understood as a MIME type
image/tiff by most of the MUAs. 

The extensions are actually needed to meet the new specification which
ITU-T had done, but the new extensions also introduce impatibility and IPR
possible clashes. 

Dave Crocker suggest as a first prroximation solution to skim down the
core specification to a "safe" subset, and pursue the other issues
separately, with a separate MIME type. 

Scott Forshee suggested also that other focus has been on JPEG-2000
specifications , and work is progressing on a different (planned) MIME
type including MRC capabilities.  However igher level features of
JPEG-2000 are generally not widely deployed. He proposed the wg to
reconsider JPEG-2000 as an alternate to TIFF-FX. Moreover, part of the
reason for Adobe's objections are to keep the use of TIFF freely
available. 

There were objections to this proposal, stating the JPEG-2000 is not yet
in good shape, has not yet a MIME type registered, too, and its wide
deployment is not existing at the moment. 

A discussion followed, considering if one should simply use the version
label into MIME typ definition to define which level of TIFF is being
used, or just a totally new type. 

Claudio Allocchio suggested that image/tiff should be used onlyfor minimum
interoperable features and anything else should have a different name and
label; this will have to happen for TIFF-7 in any case. 

Lloyd McIntyre suggested as simple solution to revert to previously
registered version of TIFF, i.e. TIFF 6.0, excluding also any widely
deployed de facto extensions. There was a discussion on this, and Scott F.
stated that TIFF 6.0 was issued in 1992, with updates via by technical
notes, which are widely implemented.  Thus RFC 2302 is OK with the way
that Adobe and others use TIFF. We should focus on the TIFF-FX spec, to
cut it back to non-controversial features. 

At this point Claudio A. asked the wg members present at the meeting if
anyone strongly oppose the approach proposed by Dave C.? 

Larry Masinter and Johm Klensin suggested that to be concerned with what
is practised is more important than compatibility with what is registered.
"The Right Thing to do is look at reality and try to get it right". 

The wg expressed consensus on the above approach. This consensus need to be
confirmed by the mailing list.

Claudio A. summarised the conclusions to be reported into the minues, and to
facilitate the understanding of the approach by anybody including those not
present at the meeting:
 
  - we must consider for interoperability test of RFC2301 also existing 
    mail user agents (MUAs), and they should be able to read image/tiff 
    bodyparts generated bu Ifax devices. Interoperability is the choice.

  - we must also consider interoperability with existing tiff capable
    software, e.g. saving the image/tiff to a file and reading it with ...
    Photoshop, and other tiff files readers.

 - we should produce a new interoperability report, and based on this
   we should detail the revision of RFC2301, to fit any feature which
   proved to interoperate in all above cases, even if not included in
   basic TIFF 6.0 specification.

 - thus existing tiff-fx Ifax devices go beyond this, as they my generate
   extensions which do not interoperate correctly with the above

 - thus we should define how to create a NEW format (both for files and 
   for MIME readers) with a different name which may be tiff-fx, or totally
   different, to make clear to implementers and devices that "this is an
   extended new format" (even if based on tiff in origin).

 - the reason for removing from RFC2301 revision some features is
   because they do not interoperate on the global service, even if they
   proved to interoperate among Ifax implementaions.

 - the "recuded set" specification will be submitted for Draft Standard

 - we should, at the same time, produce a new "extended specification"
   docuement, which includes the extensions existing in RFC2301 and
   dropped in the Draft Standard document, and might also include the
   further extensions proposed for "full mode". This document(s) should
   also define a different MIME type registration for this extended
   specification. This new specification should go as Proposed Standard

 - we need to investigate if it is possible to declare RFC1301 "Updated" 
   by the new Draft Standard document, at least until the new "Proposed
   Standard" document obsoletes RFC2301. ADs suggestions are expected.

 - we should carefully inform ITU-T of the reasons of this choice.

 - the Draft Standard version of the specification would also not have
   (apparently) IPR issues related, and the extended mode one should 
   carefully consider IPR problems while being specified.

Furthermore, we should explain, probably in the new extended document, and
probably into the implementers guide, the compatibility reasons which led
us to this choice. In fact some manufactures already have more than
profile S(simple mode) implementations with MIME type image/tiff, for
example, Profile C(color) with image/tiff, according to existing RFC2301
and RFC2302. 

After more than one hour, we closed the topic and moved forward.

3 Targeted for Draft Standard
  3.1 Service
       draft-ietf-fax-service-v2-03.txt

The document was sent to IESG on June 23rd with Interworking report
(published on June 18th); We added the request to wait for publication
until all normative dependencies are elevated to Draft Standard. We also
received AD comments which led to a new version circulated on our Mailing
List only. 

In particular, there is the reference to RFC1984 (DSN), and a reference to
RFC2301. We should thus solve TIFF issues, too.

4 Targeted for Informational 1 min (25min)
 4.1 Implementers Guide		
      draft-ietf-fax-implementers-guide-07.txt

The document was sent to IESG on Apr 10th and we had the letter from
ITU confirming that T.37 would refer the Implementer's guide.  The IETF
Last Call on July 26th until August 26th. 

It was clearly noted that also in this case we should quickly check if
there are specific references to RFC2301 which might be an issue (if
specifically refer to TIFF-FX features which could be dropped into the
Draft Standard skimmed version. 

This very same revision and check is needed for the whole set of other
documents.

5 On-going Internet-Drafts
 5.1 Gateway issue
      draft-ietf-fax-gateway-protocol-05.txt
      draft-ietf-fax-gateway-options-03.txt

Mimura-san described the main differences in the final version of gateway
documents: draft-ietf-fax-gateway-protocol-05.txt defines the minimum
requirements for Internet FAX Gateway. It defines a basic Function for the
Internet FAX Gateway, whereas draft-ietf-fax-gateway-options-03.txt
provides Information for Guideline of optional services. (See slides for
detailed differences)

Larry M. objected that the security recommendations are unclear.  It is
not explicit if the document suggest S/MIME as a MUST solution, or just a
possibility. Claudio A. reminded that also the traditional problem of
"credentials" (Sender's or Gateway's) needs to be clarified, or at least
clearly stated. Maybe it's just fine if the wording is softened - "could
be"  instead of "is". The WG agreed to issue a wg Last Call, considering
the above points as the first comment into the Last Call. 

 5.2 FFPIM
      draft-ietf-fax-ffpim-01.txt

The specification has been updated today, and mailed to the wg ML; the
main actions were to remove all editor comments, to add citation and
pointer to draft-ietf-fax-esmtp-conneg-00.txt, to add an appendix
explaining the Direct Mode and to focus on need for ÒdirectÓ
configuration, including the use of ESMTP Timely and ESMTP Conneg

Apparently no further substantial work need to be done. In particular
about direct mode, some text was added to clarify that it needs some
unusual e-mail configuration to work properly. A short discussion if all
goals were met did not discovered any missing item. The question is to be
repeated to the ML before progressing to wg LC. The only question raised
was if this document should reference the "terminal mode" documents or not
at all. Dave and some other believe that there should not be any
reference, provided the fact that there is still no consensus if the
terminal mode documents should go forward. 

      draft-ietf-fax-content-negotiation-05.txt

The WG last call ended without comments, thus we sent the request for IETF
last call to IESG on July 21st. 2001. There were no further comments from
the WG at the meeting. 

      draft-ietf-fax-esmtp-conneg-00.txt

This specification allows content negotiation to take place at the SMTP
level (i.e. between MTAs).  In particualr, this service extension is
intended for direct SMTP transfers and It can be used within an
enterprise's internal network. 

A new keyword ("CONNEG") is added to the possible EHLO values, and the
server responds with a report of the content capabilities of the device or
system that embodies the target RCPT-TO address. 

A revised version is expected by  November 2001, aiming to the WG Last Call.

      draft-ietf-fax-timely-delivery-03.txt

After some discussion with the ADs, Graham Klyne produced a new version. 
In it the feature of allowing a message to be immediately rejected for
timely delivery will be dropped.  Past experience with this kind of
feature is poor (X.400), and the use cases will generally not represent an
exacerbation of the congestion. As soon as the document is published, we
aggreed to go for the WG Last Call. 

 5.3 Terminal mode issue
      draft-maeda-faxwg-terminal-mode-goals-00.txt
      draft-maeda-faxwg-terminal-mode-protocol-00.txt
      draft-maeda-faxwg-fax-processing-status-00.txt

There were wuite a number of comments on the list about this topic. As the
author is not here we will defer further discussion to the ML. However
Claudio A. asked for some opinion of the presents. We added to our
milestones the documents in the last Minneapolis meeting. 

Larry M.objected that RFC2542 already discusses goals, so the new goals
document is largely redundant (apart from comments which are more like a
protocol specification), and asked if there is an intention to be more
specific about *requirements*? He also asked if anybody would object if we
did not pursue this document. As the author was not present, we deferred
further discussion to the ML. 

 5.4 PWG IPP Fax status report

Lloyd reported on behalf of the PWG IPP group. (see slides for a detailed
description of documents and status). Is was made clear that the activity
presetnte is carried on within the IEEE unbrella, and also that the IESG
did not accepted this activity as a possible IETF one, answering that
these activities were already covered by our wg. There was consensus from
the wg that there must be a better coordination with these external
efforts, in order to avoid any possible incomaptible products to be
developed. 

 5.5 TIFF-FX extension issue
      draft-ietf-fax-tiff-fx-Extension-1-02.txt
      (drtyre-tiff-fx-extension1-02.txt)
     darft-mcintyre-feature-schema-extension1-00.txt

After remembering that all the issues in these documents are related to
the previous discussion about TIFF and TIFF-FX issue, and that IPR
problems should be clearly investigated also for these proposed
extensions, the presentation (see slies) described the further JBIG2
extensions. 

Larry M. asked how many in the room read the draft:  One person. As such
the question was raised if we should continue the work, if there is
interest in doing it or not, provided that at a certain point the
specification will have to undego interoperability tests, and the lack of
interest could lead to a lack of implementations.  There was at the moment
no conclusion to ths question, as we need to check first the status of the
TIFF issue evolution. 

6 Miscellaneous

Finally the fax charter was updated on the IETF web pages. (July 26th 2001).
An applause came from the audience.

7 Confirmation of milestone

Here is the updated list of milestones *** (please double check it !!!) ***

Apr 2001	Submit final draft of Implementers Guide for 
		Simple and Extended mode to IESG for publication as 
		Informational.
		Done (see draft-ietf-fax-implementers-guide-07.txt sent to
		IESG on June 2001)

Jun 2001	Submit final draft for content negotiaton to IESG 
		for publication as Proposed Standard
		Done (see draft-ietf-fax-content-negotiation-05.txt sent
		to IESG on July 21st 2001)

Sep  2001	Submit final draft for timely delivery to IESG for publication
		as Proposed Standard

Sep 2001	Submit final draft for FFPIM to IESG for publication

Sep 2001	Submit final draft of gateway requirements

Nov 2001	Submit final draft of TIFF-FX extensions
Nov 2001	Submit final draft of schema for TIFF-FX extensions
These two need further work - see discussion

Jul 2001	Submit second draft of Fax status information
??? 2001	Submit second draft of Goal for Terminal Mode
??? 2001	Submit second draft of Protocol for Terminal Mode
Dec 2001	Submit final draft of Fax status information
??? 2001	Submit final draft of Goal for Terminal Mode
??? 2001	Submit Final draft of Protocol for Terminal Mode

The meeting ended at 22:04


------------------------------------------------------------------------------
Claudio Allocchio             G   A   R   R          Claudio.Allocchio@garr.it
                        Project Technical Officer
tel: +39 040 3758523      Italian Academic and       G=Claudio; S=Allocchio;
fax: +39 040 3758565        Research Network         P=garr; A=garr; C=it;

     PGP Key: http://security.fi.infn.it/cgi-bin/spgpk.pl?KeyId=0C5C2A09



From owner-ietf-fax@mail.imc.org  Thu Aug  9 13:06:51 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00368
	for <fax-archive@odin.ietf.org>; Thu, 9 Aug 2001 13:06:50 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f79GPIn26551
	for ietf-fax-bks; Thu, 9 Aug 2001 09:25:18 -0700 (PDT)
Received: from elettra.trieste.it (SYNX02.elettra.trieste.it [140.105.2.2])
	by above.proper.com (8.11.3/8.11.3) with SMTP id f79GPGN26545
	for <ietf-fax@imc.org>; Thu, 9 Aug 2001 09:25:16 -0700 (PDT)
Date: Thu, 9 Aug 2001 18:25:07 +0100
To: Kiyoshi Toyoda <ktoyoda@mb.kcom.ne.jp>
cc: ietf-fax@imc.org
In-Reply-To: <10108100605.AA00240@toyoda.mb.kcom.ne.jp>
Message-ID: <Pine.VMS.3.91-B.1010809182323.46409A-100000@SYNX02.elettra.trieste.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
Subject: Re: notes from the ietf FAX wg meeting at IETF 51
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>



> I have one comment about "7 Confirmation of milestone".
> Would you add the below as I ask you in the meeting.
> 
>  Nov 2001   Submit final draft of Esmtp-conneg for Last Call

Done!

... I knew I was missing something ! Thank you!

Claudio


From owner-ietf-fax@mail.imc.org  Thu Aug  9 17:40:47 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06116
	for <fax-archive@odin.ietf.org>; Thu, 9 Aug 2001 17:40:46 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f79KqEd02465
	for ietf-fax-bks; Thu, 9 Aug 2001 13:52:14 -0700 (PDT)
Received: from pp-mx0.tokyo.spin.ad.jp (PP-mx0.Tokyo.Spin.AD.JP [165.76.52.9])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f79KqCN02459
	for <ietf-fax@imc.org>; Thu, 9 Aug 2001 13:52:12 -0700 (PDT)
Received: from localhost (host217-33-138-213.ietf.ignite.net [217.33.138.213]) by pp-mx0.tokyo.spin.ad.jp (8.8.8+Spin/3.6W-JENS-stand2(09/30/00)) id FAA01094; Fri, 10 Aug 2001 05:52:03 +0900 (JST)
To: Claudio.Allocchio@garr.it
Cc: ietf-fax@imc.org, klensin@jck.com
Subject: Re: notes from the ietf FAX wg meeting at IETF 51
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
In-Reply-To: <Pine.VMS.3.91-B.1010809170453.46409A-100000@SYNX02.elettra.trieste.it>
References: <Pine.VMS.3.91-B.1010809170453.46409A-100000@SYNX02.elettra.trieste.it>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010810055244R.adm@ifax.attnet.ne.jp>
Date: Fri, 10 Aug 2001 05:52:44 +0900 (JST)
X-Dispatcher: imput version 20000228(IM140)
Lines: 166
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Hallo Claudio,
(and Folks)

Lots of thanks for very, very detailed ****summary****.
(Normally, one paragraph is enough within the meeting period).

There are few things that I can do for our formal minutes!!

Claudio,
may I use most of them as they are, for our formal minutes,
except for some items, which I comment below?

Folks,
As the formal minutes, I can rewrite what Claudio wrote here,
although they will be almost the same. THerefore, please confirm and check
the formal one again.

> Please drop comments and integrations to our ML. Thanks again o Graham 
> Klyne who took the base notes.

I also very much thank Graham.

I comment and add below.

TIFF-FX issue:

<snip>

Claudio,
Thank you for your thoughtful summary, regarding this issue.
I would like to remove the following Claudio's comments from the formal minutes,
because this is not mentioned at all in our meeting.

Claudio, is it acceptable to remove?

Please reply to me.

But, this is the starting point at which we have to solve TIFF-FX issue here.
Therefore, I encourage all of the IFAX implementers to read them carefully.

> Claudio A. summarised the conclusions to be reported into the minues, and to
> facilitate the understanding of the approach by anybody including those not
> present at the meeting:
>  
>   - we must consider for interoperability test of RFC2301 also existing 
>     mail user agents (MUAs), and they should be able to read image/tiff 
>     bodyparts generated bu Ifax devices. Interoperability is the choice.
> 
>   - we must also consider interoperability with existing tiff capable
>     software, e.g. saving the image/tiff to a file and reading it with ...
>     Photoshop, and other tiff files readers.
> 
>  - we should produce a new interoperability report, and based on this
>    we should detail the revision of RFC2301, to fit any feature which
>    proved to interoperate in all above cases, even if not included in
>    basic TIFF 6.0 specification.
> 
>  - thus existing tiff-fx Ifax devices go beyond this, as they my generate
>    extensions which do not interoperate correctly with the above
> 
>  - thus we should define how to create a NEW format (both for files and 
>    for MIME readers) with a different name which may be tiff-fx, or totally
>    different, to make clear to implementers and devices that "this is an
>    extended new format" (even if based on tiff in origin).
> 
>  - the reason for removing from RFC2301 revision some features is
>    because they do not interoperate on the global service, even if they
>    proved to interoperate among Ifax implementaions.
> 
>  - the "recuded set" specification will be submitted for Draft Standard
> 
>  - we should, at the same time, produce a new "extended specification"
>    docuement, which includes the extensions existing in RFC2301 and
>    dropped in the Draft Standard document, and might also include the
>    further extensions proposed for "full mode". This document(s) should
>    also define a different MIME type registration for this extended
>    specification. This new specification should go as Proposed Standard
> 
>  - we need to investigate if it is possible to declare RFC1301 "Updated" 
>    by the new Draft Standard document, at least until the new "Proposed
>    Standard" document obsoletes RFC2301. ADs suggestions are expected.

I would like to add,
Among small talks, the new Proposed Standard (or recycle standard)
includes *all* features of the existing RFC2301 and the possiblity of
compatility issues with the use of image/tiff for more than Profile S.
The recycle one(the same number) is better.

But, this is not decided. It depends on our future discussion.

>  - we should carefully inform ITU-T of the reasons of this choice.
> 
>  - the Draft Standard version of the specification would also not have
>    (apparently) IPR issues related, and the extended mode one should 
>    carefully consider IPR problems while being specified.
> 
> Furthermore, we should explain, probably in the new extended document, and
> probably into the implementers guide, the compatibility reasons which led
> us to this choice. In fact some manufactures already have more than
> profile S(simple mode) implementations with MIME type image/tiff, for
> example, Profile C(color) with image/tiff, according to existing RFC2301
> and RFC2302.

That's right. Therefore, please take them carefully.

> 3 Targeted for Draft Standard
>   3.1 Service
>        draft-ietf-fax-service-v2-03.txt

> In particular, there is the reference to RFC1984 (DSN), and a reference to
> RFC2301. We should thus solve TIFF issues, too.

I think Ned commented the editors of DSN is now preparing the new I-D.
1984 -> 1894

> 5 On-going Internet-Drafts
>  5.1 Gateway issue
>       draft-ietf-fax-gateway-protocol-05.txt
>       draft-ietf-fax-gateway-options-03.txt

<snip>

> Larry M. objected that the security recommendations are unclear.  It is
> not explicit if the document suggest S/MIME as a MUST solution, or just a
> possibility. Claudio A. reminded that also the traditional problem of
> "credentials" (Sender's or Gateway's) needs to be clarified, or at least
> clearly stated. Maybe it's just fine if the wording is softened - "could
> be"  instead of "is". The WG agreed to issue a wg Last Call, considering
> the above points as the first comment into the Last Call. 

I remember that there was a comment about it.
If my understanding is correct, updating the new ones are not necessary
at that time for the WG LCs. Am I right?

But, the modification is easy: "could be" instead of "is".

>  5.5 TIFF-FX extension issue
>       draft-ietf-fax-tiff-fx-Extension-1-02.txt
>       (drtyre-tiff-fx-extension1-02.txt)
>      darft-mcintyre-feature-schema-extension1-00.txt

<snip>

> Larry M. asked how many in the room read the draft:  One person. As such
> the question was raised if we should continue the work, if there is
> interest in doing it or not, provided that at a certain point the
> specification will have to undego interoperability tests, and the lack of
> interest could lead to a lack of implementations.  There was at the moment
> no conclusion to ths question, as we need to check first the status of the
> TIFF issue evolution. 

At the meeting, personally, I commented the extension of resolution are
at least important for IFAX implenters. Because RFC2301 only supports up to
400x400dpi.

> 7 Confirmation of milestone

> Sep 2001	Submit final draft of gateway requirements

Mimura-san,
Do you modify your I-D as the above suggestion?

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
tamura@toda.ricoh.co.jp


From owner-ietf-fax@mail.imc.org  Thu Aug  9 19:18:44 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07251
	for <fax-archive@odin.ietf.org>; Thu, 9 Aug 2001 19:18:43 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f79MVZX04427
	for ietf-fax-bks; Thu, 9 Aug 2001 15:31:35 -0700 (PDT)
Received: from adobe.com (smtp-relay-1.adobe.com [192.150.11.1])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f79MVYN04423
	for <ietf-fax@imc.org>; Thu, 9 Aug 2001 15:31:34 -0700 (PDT)
Received: from inner-relay-2.corp.adobe.com ([153.32.1.52])
	by adobe.com (1.0.0/8.11.4) with ESMTP id f79MVwB01282
	for <ietf-fax@imc.org>; Thu, 9 Aug 2001 15:31:58 -0700 (PDT)
Received: from mailsj-v1.corp.adobe.com (mailsj-dev.corp.adobe.com [153.32.1.192])
	by inner-relay-2.corp.adobe.com (8.11.4/8.11.4) with ESMTP id f79MVAb05955
	for <ietf-fax@imc.org>; Thu, 9 Aug 2001 15:31:11 -0700 (PDT)
Received: from [130.248.17.135] ([130.248.17.135]) by
          mailsj-v1.corp.adobe.com (Netscape Messaging Server 4.15 v1 Jul
          11 2001 16:32:57) with ESMTP id GHTNW600.DC8; Thu, 9 Aug 2001
          15:31:18 -0700 
Mime-Version: 1.0
X-Sender: sfoshee@mailsj-v1.corp.adobe.com
Message-Id: <p04320405b798bc5dd525@[130.248.17.135]>
In-Reply-To: <20010810055244R.adm@ifax.attnet.ne.jp>
References: 
 <Pine.VMS.3.91-B.1010809170453.46409A-100000@SYNX02.elettra.trieste.it>
 <20010810055244R.adm@ifax.attnet.ne.jp>
Date: Thu, 9 Aug 2001 15:27:48 -0700
To: Hiroshi Tamura <tamura@toda.ricoh.co.jp>, Claudio.Allocchio@garr.it
From: Scott Foshee <sfoshee@Adobe.COM>
Subject: Re: notes from the ietf FAX wg meeting at IETF 51
Cc: ietf-fax@imc.org, klensin@jck.com
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


Hiroshi,

I thought Claudio's summary was reasonably ok and I believe I 
followed his comments.  However, I am having some trouble with the 
items below.

At 5:52 AM +0900 8/10/01, Hiroshi Tamura wrote:
>Hallo Claudio,
>(and Folks)
>
>Lots of thanks for very, very detailed ****summary****.
>(Normally, one paragraph is enough within the meeting period).
>
>There are few things that I can do for our formal minutes!!
>
>Claudio,
>may I use most of them as they are, for our formal minutes,
>except for some items, which I comment below?
>
>Folks,
>As the formal minutes, I can rewrite what Claudio wrote here,
>although they will be almost the same. THerefore, please confirm and check
>the formal one again.
>
>>  Please drop comments and integrations to our ML. Thanks again o Graham
>>  Klyne who took the base notes.
>
>I also very much thank Graham.
>
>I comment and add below.
>
>TIFF-FX issue:
>
><snip>
>
>Claudio,
>Thank you for your thoughtful summary, regarding this issue.
>I would like to remove the following Claudio's comments from the 
>formal minutes,
>because this is not mentioned at all in our meeting.
>
>Claudio, is it acceptable to remove?

What is to be removed?

>
>Please reply to me.
>
>But, this is the starting point at which we have to solve TIFF-FX issue here.
>Therefore, I encourage all of the IFAX implementers to read them carefully.
>
>>  Claudio A. summarised the conclusions to be reported into the minues, and to
>>  facilitate the understanding of the approach by anybody including those not
>>  present at the meeting:
>> 
>>    - we must consider for interoperability test of RFC2301 also existing
>>      mail user agents (MUAs), and they should be able to read image/tiff
>>      bodyparts generated bu Ifax devices. Interoperability is the choice.
>>
>>    - we must also consider interoperability with existing tiff capable
>>      software, e.g. saving the image/tiff to a file and reading it with ...
>>      Photoshop, and other tiff files readers.
>>
>>   - we should produce a new interoperability report, and based on this
>>     we should detail the revision of RFC2301, to fit any feature which
>>     proved to interoperate in all above cases, even if not included in
>>     basic TIFF 6.0 specification.
>>
>>   - thus existing tiff-fx Ifax devices go beyond this, as they my generate
>>     extensions which do not interoperate correctly with the above
>>
>>   - thus we should define how to create a NEW format (both for files and
>>     for MIME readers) with a different name which may be tiff-fx, or totally
>>     different, to make clear to implementers and devices that "this is an
>>     extended new format" (even if based on tiff in origin).
>>
>>   - the reason for removing from RFC2301 revision some features is
>>     because they do not interoperate on the global service, even if they
>>     proved to interoperate among Ifax implementaions.
>>
>>   - the "recuded set" specification will be submitted for Draft Standard
>>
>>   - we should, at the same time, produce a new "extended specification"
>>     docuement, which includes the extensions existing in RFC2301 and
>>     dropped in the Draft Standard document, and might also include the
>>     further extensions proposed for "full mode". This document(s) should
>>     also define a different MIME type registration for this extended
>>     specification. This new specification should go as Proposed Standard
>>
>>   - we need to investigate if it is possible to declare RFC1301 "Updated"
>>     by the new Draft Standard document, at least until the new "Proposed
>>     Standard" document obsoletes RFC2301. ADs suggestions are expected.
>
>I would like to add,
>Among small talks, the new Proposed Standard (or recycle standard)
>includes *all* features of the existing RFC2301 and the possiblity of
>compatility issues with the use of image/tiff for more than Profile S.
>The recycle one(the same number) is better.

This paragraph was not clear to me.  I do not recall your comments as 
part of the WG discussion.  Can you clarify?

>
>But, this is not decided. It depends on our future discussion.
>
>>   - we should carefully inform ITU-T of the reasons of this choice.
>>
>>   - the Draft Standard version of the specification would also not have
>>     (apparently) IPR issues related, and the extended mode one should
>>     carefully consider IPR problems while being specified.
>>
>>  Furthermore, we should explain, probably in the new extended document, and
>>  probably into the implementers guide, the compatibility reasons which led
>>  us to this choice. In fact some manufactures already have more than
>>  profile S(simple mode) implementations with MIME type image/tiff, for
>>  example, Profile C(color) with image/tiff, according to existing RFC2301
>>  and RFC2302.
>
>That's right. Therefore, please take them carefully.
>
>>  3 Targeted for Draft Standard
>>    3.1 Service
>>         draft-ietf-fax-service-v2-03.txt
>
>>  In particular, there is the reference to RFC1984 (DSN), and a reference to
>>  RFC2301. We should thus solve TIFF issues, too.
>
>I think Ned commented the editors of DSN is now preparing the new I-D.
>1984 -> 1894
>
>>  5 On-going Internet-Drafts
>>   5.1 Gateway issue
>>        draft-ietf-fax-gateway-protocol-05.txt
>>        draft-ietf-fax-gateway-options-03.txt
>
><snip>
>
>>  Larry M. objected that the security recommendations are unclear.  It is
>>  not explicit if the document suggest S/MIME as a MUST solution, or just a
>>  possibility. Claudio A. reminded that also the traditional problem of
>>  "credentials" (Sender's or Gateway's) needs to be clarified, or at least
>>  clearly stated. Maybe it's just fine if the wording is softened - "could
>>  be"  instead of "is". The WG agreed to issue a wg Last Call, considering
>>  the above points as the first comment into the Last Call.
>
>I remember that there was a comment about it.
>If my understanding is correct, updating the new ones are not necessary
>at that time for the WG LCs. Am I right?
>
>But, the modification is easy: "could be" instead of "is".
>
>>   5.5 TIFF-FX extension issue
>>        draft-ietf-fax-tiff-fx-Extension-1-02.txt
>>        (drtyre-tiff-fx-extension1-02.txt)
>>       darft-mcintyre-feature-schema-extension1-00.txt
>
><snip>
>
>>  Larry M. asked how many in the room read the draft:  One person. As such
>>  the question was raised if we should continue the work, if there is
>>  interest in doing it or not, provided that at a certain point the
>>  specification will have to undego interoperability tests, and the lack of
>>  interest could lead to a lack of implementations.  There was at the moment
>>  no conclusion to ths question, as we need to check first the status of the
>>  TIFF issue evolution.
>
>At the meeting, personally, I commented the extension of resolution are
>at least important for IFAX implenters. Because RFC2301 only supports up to
>400x400dpi.
>
>>  7 Confirmation of milestone
>
>>  Sep 2001	Submit final draft of gateway requirements
>
>Mimura-san,
>Do you modify your I-D as the above suggestion?
>
>Regards,
>--
>Hiroshi Tamura, Co-chair of IETF-FAX WG
>tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Fri Aug 10 02:46:04 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29850
	for <fax-archive@odin.ietf.org>; Fri, 10 Aug 2001 02:46:03 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7A638S12469
	for ietf-fax-bks; Thu, 9 Aug 2001 23:03:08 -0700 (PDT)
Received: from pp-mx0.tokyo.spin.ad.jp (PP-mx0.Tokyo.Spin.AD.JP [165.76.52.9])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7A635N12457
	for <ietf-fax@imc.org>; Thu, 9 Aug 2001 23:03:05 -0700 (PDT)
Received: from localhost (host217-33-138-213.ietf.ignite.net [217.33.138.213]) by pp-mx0.tokyo.spin.ad.jp (8.8.8+Spin/3.6W-JENS-stand2(09/30/00)) id PAA16891; Fri, 10 Aug 2001 15:02:53 +0900 (JST)
To: sfoshee@Adobe.COM
Cc: Claudio.Allocchio@garr.it, ietf-fax@imc.org, klensin@jck.com
Subject: Re: notes from the ietf FAX wg meeting at IETF 51
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
In-Reply-To: <p04320405b798bc5dd525@[130.248.17.135]>
References: <Pine.VMS.3.91-B.1010809170453.46409A-100000@SYNX02.elettra.trieste.it>
	<20010810055244R.adm@ifax.attnet.ne.jp>
	<p04320405b798bc5dd525@[130.248.17.135]>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010810150318R.adm@ifax.attnet.ne.jp>
Date: Fri, 10 Aug 2001 15:03:18 +0900 (JST)
X-Dispatcher: imput version 20000228(IM140)
Lines: 95
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Scott,

> What is to be removed?

From the next line,

Claudio says:
> Claudio A. summarised the conclusions to be reported into the minues, and to
> facilitate the understanding of the approach by anybody including those not
> present at the meeting:
>  
>   - we must consider for interoperability test of RFC2301 also existing 
>     mail user agents (MUAs), and they should be able to read image/tiff 
>     bodyparts generated bu Ifax devices. Interoperability is the choice.
> 
>   - we must also consider interoperability with existing tiff capable
>     software, e.g. saving the image/tiff to a file and reading it with ...
>     Photoshop, and other tiff files readers.
> 
>  - we should produce a new interoperability report, and based on this
>    we should detail the revision of RFC2301, to fit any feature which
>    proved to interoperate in all above cases, even if not included in
>    basic TIFF 6.0 specification.
> 
>  - thus existing tiff-fx Ifax devices go beyond this, as they my generate
>    extensions which do not interoperate correctly with the above
> 
>  - thus we should define how to create a NEW format (both for files and 
>    for MIME readers) with a different name which may be tiff-fx, or totally
>    different, to make clear to implementers and devices that "this is an
>    extended new format" (even if based on tiff in origin).
> 
>  - the reason for removing from RFC2301 revision some features is
>    because they do not interoperate on the global service, even if they
>    proved to interoperate among Ifax implementaions.
> 
>  - the "recuded set" specification will be submitted for Draft Standard
> 
>  - we should, at the same time, produce a new "extended specification"
>    docuement, which includes the extensions existing in RFC2301 and
>    dropped in the Draft Standard document, and might also include the
>    further extensions proposed for "full mode". This document(s) should
>    also define a different MIME type registration for this extended
>    specification. This new specification should go as Proposed Standard
> 
>  - we need to investigate if it is possible to declare RFC1301 "Updated" 
>    by the new Draft Standard document, at least until the new "Proposed
>    Standard" document obsoletes RFC2301. ADs suggestions are expected.
> 
>  - we should carefully inform ITU-T of the reasons of this choice.
> 
>  - the Draft Standard version of the specification would also not have
>    (apparently) IPR issues related, and the extended mode one should 
>    carefully consider IPR problems while being specified.
> 
> Furthermore, we should explain, probably in the new extended document, and
> probably into the implementers guide, the compatibility reasons which led
> us to this choice. In fact some manufactures already have more than
> profile S(simple mode) implementations with MIME type image/tiff, for
> example, Profile C(color) with image/tiff, according to existing RFC2301
> and RFC2302. 

By the above line.

These explain our current situation very well.
It comes from the mail and the talk between Cluadio and me, AFTER the meeting.
But, it is not discussed in the meeting.
Therefore, I propose to remove them in our minutes.

Claudio,
Please comment it.

> >I would like to add,
> >Among small talks, the new Proposed Standard (or recycle standard)
> >includes *all* features of the existing RFC2301 and the possiblity of
> >compatility issues with the use of image/tiff for more than Profile S.
> >The recycle one(the same number) is better.

Scott says:
> This paragraph was not clear to me.  I do not recall your comments as 
> part of the WG discussion.  Can you clarify?

This is just my comment to the Claudio's summary(the mail).
I did not comment there.
So, I do NOT put my comment in our minutes.
It is only one idea in small talks between Claudio and me AFTER our meeting.

Scott,
Please keep trying to solve this issue.

Regards,
--
Hiroshi Tamura, Ricoh Company, LTD.
tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Fri Aug 10 04:46:43 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01477
	for <fax-archive@odin.ietf.org>; Fri, 10 Aug 2001 04:46:43 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7A7vYq01301
	for ietf-fax-bks; Fri, 10 Aug 2001 00:57:34 -0700 (PDT)
Received: from elettra.trieste.it (SYNX02.elettra.trieste.it [140.105.2.2])
	by above.proper.com (8.11.3/8.11.3) with SMTP id f7A7vWN01295
	for <ietf-fax@imc.org>; Fri, 10 Aug 2001 00:57:33 -0700 (PDT)
Date: Fri, 10 Aug 2001 09:56:05 +0100
To: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
cc: ietf-fax@imc.org, klensin@jck.com
In-Reply-To: <20010810055244R.adm@ifax.attnet.ne.jp>
Message-ID: <Pine.VMS.3.91-B.1010810095047.47060A-100000@SYNX02.elettra.trieste.it>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
From: Claudio Allocchio <Claudio.Allocchio@garr.it>
Subject: Re: notes from the ietf FAX wg meeting at IETF 51
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>



> may I use most of them as they are, for our formal minutes,
> except for some items, which I comment below?

Sure ! 

> Claudio,
> Thank you for your thoughtful summary, regarding this issue.
> I would like to remove the following Claudio's comments from the formal minutes,
> because this is not mentioned at all in our meeting.
> 
> Claudio, is it acceptable to remove?

Yes. I added it to ther note in order too have the mailing list know 
which is the possible solution we planned also in the further discussions 
about the problem. Thus consider it a "message to the mailing list"

> Among small talks, the new Proposed Standard (or recycle standard)
> includes *all* features of the existing RFC2301 and the possiblity of
> compatility issues with the use of image/tiff for more than Profile S.
> The recycle one(the same number) is better.
> 

Ok, for the minutes can be fine: we already have the details on the ML.

> 
 Any other correction is fine, too!

Regards
Claudio Allocchio

PS: I'll be off line for 2 weeks now. Thus no e-mail answers during this 
period!


From owner-ietf-fax@mail.imc.org  Fri Aug 10 04:59:55 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01591
	for <fax-archive@odin.ietf.org>; Fri, 10 Aug 2001 04:59:54 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7A8Nb502757
	for ietf-fax-bks; Fri, 10 Aug 2001 01:23:37 -0700 (PDT)
Received: from pp-mx0.tokyo.spin.ad.jp (PP-mx0.Tokyo.Spin.AD.JP [165.76.52.9])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7A8NZN02748
	for <ietf-fax@imc.org>; Fri, 10 Aug 2001 01:23:35 -0700 (PDT)
Received: from localhost (host217-33-138-213.ietf.ignite.net [217.33.138.213]) by pp-mx0.tokyo.spin.ad.jp (8.8.8+Spin/3.6W-JENS-stand2(09/30/00)) id RAA00473; Fri, 10 Aug 2001 17:23:29 +0900 (JST)
To: Claudio.Allocchio@garr.it
Cc: ietf-fax@imc.org
Subject: Re: notes from the ietf FAX wg meeting at IETF 51
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
In-Reply-To: <Pine.VMS.3.91-B.1010810095047.47060A-100000@SYNX02.elettra.trieste.it>
References: <20010810055244R.adm@ifax.attnet.ne.jp>
	<Pine.VMS.3.91-B.1010810095047.47060A-100000@SYNX02.elettra.trieste.it>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010810172339M.adm@ifax.attnet.ne.jp>
Date: Fri, 10 Aug 2001 17:23:39 +0900 (JST)
X-Dispatcher: imput version 20000228(IM140)
Lines: 33
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Hallo Claudio,

> > may I use most of them as they are, for our formal minutes,
> > except for some items, which I comment below?

> Sure ! 

Thanks. It will take only few hours to complete the formal one.

> > I would like to remove the following Claudio's comments from the formal minutes,
> > because this is not mentioned at all in our meeting.

> > Claudio, is it acceptable to remove?
> 
> Yes. I added it to ther note in order too have the mailing list know 
> which is the possible solution we planned also in the further discussions 
> about the problem. Thus consider it a "message to the mailing list"

Completely right.

To all:
Please read it carefully and if you have comments, please say it!

> PS: I'll be off line for 2 weeks now. Thus no e-mail answers during this 
> period!

Enjoy your holiday!

Regards,
--
Hiroshi Tamura, Ricoh Company, LTD.
tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Tue Aug 14 13:21:14 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10938
	for <fax-archive@odin.ietf.org>; Tue, 14 Aug 2001 13:21:13 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7EGTkq20555
	for ietf-fax-bks; Tue, 14 Aug 2001 09:29:46 -0700 (PDT)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7EGTjN20551
	for <ietf-fax@imc.org>; Tue, 14 Aug 2001 09:29:45 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-4.cisco.com (8.11.3/8.9.1) with ESMTP id f7EGTrn08741
	for <ietf-fax@imc.org>; Tue, 14 Aug 2001 09:29:53 -0700 (PDT)
Received: from DWINGW2K (dhcp-128-107-139-165.cisco.com [128.107.139.165])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAG14277;
	Tue, 14 Aug 2001 09:29:41 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "IETF Internet Fax WG" <ietf-fax@imc.org>
Subject: CNN: IETF puts brakes on TIFF-FX
Date: Tue, 14 Aug 2001 09:29:41 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGGENDEEAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


> >ADOBE, XEROX TIFF SLOWS INTERNET FAX STANDARD
> >
> >
> >The Internet Engineering Task Force has slammed the brakes on its plans to
> >develop a common way of sending faxes over the Internet, due to
> >last-minute licensing problems between rivals Adobe Systems and Xerox.
> >
> http://www.cnn.com/2001/TECH/internet/08/13/adobe.xerox.tiff.idg/index.html



From owner-ietf-fax@mail.imc.org  Tue Aug 14 15:39:22 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13632
	for <fax-archive@odin.ietf.org>; Tue, 14 Aug 2001 15:39:22 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7EJ3A324138
	for ietf-fax-bks; Tue, 14 Aug 2001 12:03:10 -0700 (PDT)
Received: from jsc-ems-vws04.jsc.nasa.gov (jsc-ems-vws04.jsc.nasa.gov [139.169.39.51])
	by above.proper.com (8.11.3/8.11.3) with SMTP id f7EJ39N24133
	for <ietf-fax@imc.org>; Tue, 14 Aug 2001 12:03:09 -0700 (PDT)
Received: from 139.169.16.21 by jsc-ems-vws04.jsc.nasa.gov (InterScan E-Mail VirusWall NT); Tue, 14 Aug 2001 14:02:05 -0500 (Central Daylight Time)
Received: by jsc-ems-gws02.jsc.nasa.gov with Internet Mail Service (5.5.2448.0)
	id <Q7HAQBBH>; Tue, 14 Aug 2001 14:02:48 -0500
Message-ID: <81F639B56628D011A32D0020AFFC019007C21140@jsc-ems-mbs07.jsc.nasa.gov>
From: "COLES, RICHARD J. (JSC-EV) (LM)" <richard.j.coles1@jsc.nasa.gov>
To: "'Dan Wing'" <dwing@cisco.com>
Cc: IETF Internet Fax WG <ietf-fax@imc.org>
Subject: RE: IETF puts brakes on TIFF-FX
Date: Tue, 14 Aug 2001 14:03:02 -0500
X-Mailer: Internet Mail Service (5.5.2448.0)
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>



I read the article referenced below & pose a simple question, which, I'm
sure, will bring lots of responses:

Since the great, great majority of FAX is B&W anyway, why not release
TIFF-FX as a monochrome standard?  Then, when the snags between Xerox, Adobe
& everyone else are worked out, define a second extension, such as TIFF-CF
for "color fax".

I am probably overlooking some obvious reason why it "can't be done", but I
thought I would ask the question anyway.

Regards to all,

Richard Coles
Lockheed Martin, in support of
NASA/Johnson Space Center/Houston

I'm in this to save the Government, and therefore the TAXPAYERS (like me), a
LOT of money.

R

-----Original Message-----
From: Dan Wing [mailto:dwing@cisco.com]
Sent: Tuesday, August 14, 2001 11:30 AM
To: IETF Internet Fax WG
Subject: CNN: IETF puts brakes on TIFF-FX



> >ADOBE, XEROX TIFF SLOWS INTERNET FAX STANDARD
> >
> >
> >The Internet Engineering Task Force has slammed the brakes on its plans
to
> >develop a common way of sending faxes over the Internet, due to
> >last-minute licensing problems between rivals Adobe Systems and Xerox.
> >
>
http://www.cnn.com/2001/TECH/internet/08/13/adobe.xerox.tiff.idg/index.html


From owner-ietf-fax@mail.imc.org  Tue Aug 14 20:06:12 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17637
	for <fax-archive@odin.ietf.org>; Tue, 14 Aug 2001 20:06:12 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7ENISG00267
	for ietf-fax-bks; Tue, 14 Aug 2001 16:18:28 -0700 (PDT)
Received: from pasiphae.eastgw.xerox.com (pasiphae.xerox.com [208.140.33.23])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7ENH6N00244
	for <ietf-fax@imc.org>; Tue, 14 Aug 2001 16:17:06 -0700 (PDT)
Received: from godzilla.ADOC.xerox.com (godzilla.ADOC.xerox.com [13.242.128.10])
	by pasiphae.eastgw.xerox.com (8.9.3/8.9.3) with ESMTP id TAA07546;
	Tue, 14 Aug 2001 19:16:28 -0400 (EDT)
Received: from mercury.adoc.xerox.com (mercury [13.242.100.20])
	by godzilla.ADOC.xerox.com (8.8.8+Sun/8.8.8/ADOC-HUB-1.7) with ESMTP id QAA17720;
	Tue, 14 Aug 2001 16:14:52 -0700 (PDT)
Received: by mercury.ADOC.xerox.com with Internet Mail Service (5.5.2653.19)
	id <QN3PW7HT>; Tue, 14 Aug 2001 16:14:52 -0700
Message-ID: <51B8ABCE456FD111899900805F6FD6EE067A352A@mercury.ADOC.xerox.com>
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
To: "'IETF - fax WG dl'" <ietf-fax@imc.org>,
        "'IETF - John Klensin (IAB Chair)'" <klensin@jck.com>
Cc: "'PWG - IPPFax DL'" <ifx@pwg.org>
Subject: FW: notes from the ietf FAX wg meeting at IETF 51
Date: Tue, 14 Aug 2001 16:14:51 -0700
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C12516.EB4AF170"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C12516.EB4AF170
Content-Type: text/plain;
	charset="iso-8859-1"

Claudio and Tamura-san
My thanks to you and Graham for the excellent job in capturing the meeting
proceedings and result.
Please allow me to suggest a few clarifications below.

Regards,
Lloyd 

> -----Original Message-----
> From: Claudio Allocchio [mailto:Claudio.Allocchio@garr.it]
> Sent: Thursday, August 09, 2001 9:26 AM
> To: ietf-fax@imc.org
> Cc: klensin@jck.com
> Subject: notes from the ietf FAX wg meeting at IETF 51
> 
> 
> 
---snip---
> 
>  2.2 TIFF-FX
>       draft-ietf-fax-tiff-fx-09.txt
>       draft-ietf-fax-tiff-regbis-02.txt
> 
---snip---
> The question now is: can we meet all these constrains? Is TIFF the right
> choice to accomplish them? 
The second sentence was not an issued raised by the IAB chair, in fact one
individual raised this issue. Please consider deleting the second sentence
or revising to read as follows:
"The question now is: can we meet all these constrains? One individual asked
whether TIFF was the right choice to accomplish them?"

> Basic TIFF does not support colors, and different resolutions, but is it
> compliant with the existing TIFF readers, and e-mail User Agents (MUAs).
Reverse the order of "is it" to read "it is".

> However, if we want to cover also the "extensions" that ITU-T is
> requesting for fax service (e.g. colors, resolutions, etc...) Basic TIFF
> is not enough, and it will need extensions. 
Given that accommodation of ITU-T color and higher quality encodings was a
component of the WG charter, this sentence may be reworded to convey less of
an impression that it was an afterthought. Please consider the following
revision:
"Basic TIFF was not enough to accommodate color and higher quality ITU-T
encodings, consequently extensions were needed."

>                                                These extensions were
> specified into TIFF-FX, and ITU-T decided to adopt and reference it.
For completeness, please append "for their Internet Fax standard" to this
sentence. It should now read:
"These extensions were specified into TIFF-FX, and ITU-T decided to adopt
and reference it for their Internet Fax standard."

> However TIFF-FX is already beyond Basic TIFF. 
> 
> Actually there are already de facto extensions to basic TIFF
> specifications which are publicly available, and widely 
> deployed within
> both TIFF readers and MUAs. All there de facto extensions are 
> currently
> used in MIME type "image/tiff" and there are not interoperability
> problems. 
The statement of no interoperability problems with all the de facto
extensions is inaccurate, since some deployed viewers will not read all the
extensions. Please reword the second sentence similar to the following:
"All the de facto extensions are currently used in MIME type "image/tiff"
and some have no interoperability problems."

>          However the extensions intriduced into TIFF-FX are a superset,
> and thus only some Ifax devices can correctly handle them. 
A correction and softening is warranted, given that it is not only Ifax
devices that are capable of reading TIFF-FX files and the limited
readability is not an unusual issue with new extensions in general. Consider
the following:
"The extensions introduced into TIFF-FX are a superset, which are viewable
by a limited set of Ifax devices and software applications."

It is important to convey the fact that the WG took deliberate steps to
avoid incompatibility resulting from addition of new encodings by redefining
the image/tiff MIME type (i.e. RFC2302) to include an application parameter.
The results were not quite satisfactory, however, the issue was addressed
and steps were taken. Accordingly, please consider insertion of the
following paragraph: 

"To avoid interoperability issues arising from introduction of the extended
color and high quality super set, the image/tiff MIME type was revised to
add application parameters. The image/tiff application parameters serve to
alert viewers to the presence of the TIFF-FX superset. Recent disclosures,
however, indicate that many readers do not pay attention to MIME application
parameters. It is the inconsistent usage of application parameters that is
at the heart of TIFF-FX incompatibility with image/tiff viewers."

> 
> So, the IESG and IAB would like the WG to review and 
> document, as a condition
> for advancing the TIFF specification to Draft Standard:
> 
>  - Whether the choice of "interoperation with e-mail" versus 
> "interoperation
>    with fax" is the right one
>  - whether a mostly-fax-only TIFF variation is the right choice
>  - Whether this should be image/tiff or image/tifffx (or equivalent)
Clarify as follows:
 "- Whether the MIME sub-type should be image/tiff or image/tifffx (or
equivalent)"

>  - hether the interoperability profile is right given these issues
Please clarify, I do not understand what is being said?

>  - and any other similar tradeoffs that might have been made 
> without full
>    evaluation.

---snip---
The paragraph below appears to be lacking context of what the IPR issue is,
please prefix it with the following:
"In December 2000 Adobe provided notification of its believe that the
TIFF-FX specification exceeds the scope of its 1997 IETF license grant for
TIFF-FX development <http://www.ietf.org/ietf/IPR/Adobe-TIFF>. Inclusion of
the extended encodings within TIFF-FX was identified as reason for the claim
of exceeded scope. The validity of this claim has been questioned, given
that the grant contains no constraint on extensions within TIFF-FX. The fact
that Abode co-authored both the TIFF-FX and the revised MIME image/tiff
specifications makes it more difficult to understand the claim.
Additionally, it may be said that the claim is somewhat late, given that
TIFF-FX was issued as Proposed Standard in December 1998."  

> Adobe:  the solution appears to be to have Adobe include the 
> new TIFF-FX
> encodings in TIFF-7, but Adobe has not committed to produce 
> TIFF-7 and It
> is not clear what produces that commitment. Moreover, even if they do
> TIFF-7, they will not commit to including the TIFF-FX 
> features until at
> least Xerox releases rights to the encoding techniques for all uses of
> TIFF, not just fax and Xerox (or maybe IETF) apply formally 
> to Adobe to
> have the features and tags included. At last, but not the 
> least, no one at
> this IETF can commit Adobe. 
In light of the attached license statement, which clearly states that Xerox
grants MRC license use within TIFF-FX and without any application space
restrictions, please correct the 2nd sentence by inserting "MRC" between
"the encoding" and changing "not just fax and Xerox (or maybe IETF) apply"
to "not just TIFF-FX, and apply". The sentence should now read:
"Moreover, even if they do TIFF-7, they will not commit to including the
TIFF-FX features until at least Xerox releases rights to the MRC encoding
techniques for all uses of TIFF, not just TIFF-FX, and apply formally to
Adobe to have the features and tags included."

> 
> Xerox: Xerox is willing to release rights for all uses in 
> TIFF if Adobe
> will adopt them and include them in TIFF-7. But no one here can commit
> Xerox either. 
> 
> Thus it seems a viable solution currently in a deadlock waiting for
> somebody to make the first move. 
> 
---snip---
> 
> The discussion of the problem and the WG conclusions.
> -------------------------------------------------
> 
Consider constraining this section to only WG conclusions and procedures to
be followed, removing the detailed he said/she said commentary. This
translates to deleting all items prior to the paragraph that starts "Claudio
A. summarised the conclusions to be reported into the minues,". 
The revised title might read as follows:
"WG meeting conclusions and procedures to be followed"
 ----------------------------------------------------

This would be followed by a restructured, consolidated and clarified body as
below.

A summary of the meeting's rough consensus, along with the procedures to be
followed, is provided below with "rc" identifying rough consensus items and
"p" identifying procedure items:
rc - Interoperability with email was considered the most important choice
between email or fax interoperability.

p  - Level of interoperability should be established by conducting a test of
RFC2301 (more appropriately draft-ietf-fax-tiff-fx-09.txt) using existing
mail user agents (MUAs) and tiff capable software applications such as
PhotoShop and other tiff viewers. The software viewer test may be
accommodated by saving the RFC2301 image/tiff stream to a file with .tif or
other appropriate tiff extension.

p  - An interoperability report should be generated and used to document the
set of interoperable TIFF-FX encoding parameters, such as coder, resolution,
paper size and color components.

p  - One of the four options below should be selected for the
specification(s) that will move forward through the standards tack process:
     1. Full TIFF-FX: - retain the currently defined TIFF-FX draft without
modification of the encoding set and define both a new MIME type (e.g.
image/tifffx or image/tifx) and a new file extension (e.g. .tifx or .tfx).
The new MIME type and extension circumvents interoperability issues with
TIFF 6.0. 
        Advantages: i) Retention of color and high quality encodings, ii) no
disruption of IFax products under deployment, and iii) a single integrated
specification.
        Disadvantages: i) Licensing issues to be resolved, and ii)
unpredictable approval schedule due to license resolution. 

     2. Interoperable TIFF-FX: - use the new interoperability document to
generate a TIFF-FX subset that is image/tiff interoperable, retaining the
current image/tiff MIME type. 
        Advantages: i) No licensing issues, and ii) predictable approval
schedule.
        Disadvantages: i) Loss of color and high quality encodings, ii)
disruption of IFax products under deployment.

     3. Interoperable and non-Interoperable TIFF-FX: - use the new
interoperability document to generate two subsets, a) Interoperable TIFF-FX,
as per #2, and b) non-Interoperable TIFF-FX, which is composed of the
remaining encoding subset. As with Full TIFF-FX, define both a new MIME type
and a new file extension for the non-Interoperable TIFF-FX.
        Advantages: i) Base-level black-and-white has no licensing issues,
ii) predictable base-level approval schedule iii) retention of color and
high quality encodings, iv) minimal disruption of IFax products under
deployment.
        Disadvantages: i) Licensing issues to be resolved for color & high
quality, ii) unpredictable color & high quality approval schedule, iii) two
disjoined specifications.

     4. Interoperable and Full TIFF-FX: - this is a combination of options 1
and 2.
        Advantages: i) Base-level black-and-white has no licensing issues,
ii) predictable base-level approval schedule iii) retention of color and
high quality encodings, iv) no disruption of IFax products under deployment,
and v) base-level specification may be phased out as viewers advance.
        Disadvantages: i) Licensing issues to be resolved for color & high
quality, ii) unpredictable color & high quality approval schedule.

rc - Option 2, Interoperable TIFF-FX, was selected to move forward at this
time.

p  - Justification of the selection must be documented and communicated to
the ITU.

p  - Both the resulting specification and the Implementors Guide should
contain explanation of the interoperability issues and countermeasures.

p  - The resulting specification(s) may be resubmitted to the IESG for Draft
Standard consideration if there are draft-ietf-fax-tiff-fx-09.txt
function/feature deletions or no changes. This means that Full TIFF-FX, with
no changes, and both the Interoperable TIFF-FX and non-Interoperable TIFF-FX
subsets, without any additions, may be resubmitted to the IESG for Draft
Standard consideration. Any required specification additions shall result in
recycle as Proposed Standard. 

p  - Resolution of IPR issues associated with Full TIFF-FX and
non-Interoperable TIFF-FX needs to progress in parallel with the above
activates and the ITU should be kept informed. 

---snip---

> 5.5 TIFF-FX extension issue
>      draft-ietf-fax-tiff-fx-Extension-1-02.txt
>      (drtyre-tiff-fx-extension1-02.txt)
>     darft-mcintyre-feature-schema-extension1-00.txt

> After remembering that all the issues in these documents are related to
> the previous discussion about TIFF and TIFF-FX issue, and that IPR
>problems should be clearly investigated also for these proposed
> extensions, the presentation (see slies) described the further JBIG2
> extensions. 

> Larry M. asked how many in the room read the draft:  One person. As such
> the question was raised if we should continue the work, if there is
> interest in doing it or not, provided that at a certain point the
> specification will have to undego interoperability tests, and the lack of
> interest could lead to a lack of implementations.  There was at the moment
> no conclusion to ths question, as we need to check first the status of the
> TIFF issue evolution.
The second paragraph should be depersonalized and clarified to note that
there was confusion as to which specification was being addressed by the
question of number of reviewers. The question was asked toward the end of
the Schema, not the TIFF-FX Extension presentation. The respondent was a
reviewer of the Schema extension, which is a very new draft with little time
for review. Revise as follows:
"Toward the end of the Schema extension presentation a member ask how many
had read the draft, there was no clarifications as which draft was being
referenced. There was acknowledgement from on member who had reviewed the
Schema drat. The requestor then asked whether the work should be continued,
without much response. No conclusions could be drawn."


------_=_NextPart_000_01C12516.EB4AF170
Content-Type: text/plain;
	name="Xerox IETF IPR statement.txt"
Content-Disposition: attachment;
	filename="Xerox IETF IPR statement.txt"


From http://www.ietf.org/ietf/IPR/XEROX-RFC2301

The following was conveyed via email on September 9, 1999 by Clarke Wixon
Patent Attorney, Xerox


Mr. Stephen Coya
Executive Director
Internet Engineering Task Force
c/o Corporation for National Research Initiatives
1895 Preston White Drive, Suite 100
Reston, Virginia 20191-5434

Re:     IETF RFC 2301 (TIFF-FX) IPR Statement

Dear Mr. Coya:

Xerox is currently aware of two U.S. Patents which may relate to implementations of
the IETF RFC 2301 (TIFF-FX) standard. U.S. Patent No. Re35,657 is owned by Xerox
Corporation. U.S. Patent No. 5,778,092 is owned by ScanSoft, Inc., but Xerox has
rights to sublicense the technology for these purposes.

To the extent that Xerox's existing intellectual property rights under the above two
patents may cover the implementation of a product compliant with the TIFF-FX
standard, Xerox agrees to provide, upon request, a royalty-free, world-wide,
non-exclusive license under certain claims of the above two patents (not including
the segmentation technology described in the specification and set forth in claims
2-4, 7, 8, or 12-14 of U.S. Patent No. 5,778,092, which is not considered to be an
essential technology for the implementation of the TIFF-FX standard) for the purpose
of making, having made, using, selling, offering for sale, or otherwise disposing of
a product implementing the TIFF-FX standard, and only to the limited extent
necessary for the product to comply with the TIFF-FX standard.

Any license granted by Xerox under this Statement shall be subject to the following
condition: any party receiving such a grant from Xerox must agree to grant Xerox
Corporation, Xerox Ltd., Fuji Xerox Co. Ltd., Modi Xerox Limited and any
corporation, firm, partnership, individual, or other form of business organization
at least forty percent (40%) owned or controlled, directly or indirectly, by Xerox
Corporation, Xerox Ltd., Fuji Xerox Ltd. or Modi Xerox Limited, upon request, a
license under that party's patents relating to the TIFF-FX standard, on terms and
conditions no less favorable than those granted by Xerox to that party.

Parties interested in obtaining a license may contact:

Xerox Intellectual Property Operations (XIPO)
ATTN: MRC License Inquiries
100 Willowbrook Office Park, Bldg. 832-01A
Fairport, New York 14450  U.S.A.

Very truly yours,

/s/

Dr. Jan Jaferian
Vice President

c:      James Rafferty (IFax WG Chair) <jrafferty@worldnet.att.net>
        Keith Moore (IETF Area Director) <moore@cs.utk.edu>
        Patrik Faltstrom (IETF Area Director) <paf@swip.net>


Clarke Wixon
Patent Attorney
Xerox Corporation


------_=_NextPart_000_01C12516.EB4AF170--


From owner-ietf-fax@mail.imc.org  Tue Aug 14 21:25:14 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19100
	for <fax-archive@odin.ietf.org>; Tue, 14 Aug 2001 21:25:13 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7F0Y7O02303
	for ietf-fax-bks; Tue, 14 Aug 2001 17:34:07 -0700 (PDT)
Received: from adobe.com (smtp-relay-1.adobe.com [192.150.11.1])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7F0VVN02246
	for <ietf-fax@imc.org>; Tue, 14 Aug 2001 17:31:31 -0700 (PDT)
Received: from inner-relay-1.corp.adobe.com ([153.32.1.51])
	by adobe.com (1.0.0/8.11.4) with ESMTP id f7F0UaB26692
	for <ietf-fax@imc.org>; Tue, 14 Aug 2001 17:30:36 -0700 (PDT)
Received: from mailsj-v1.corp.adobe.com (mailsj-dev.corp.adobe.com [153.32.1.192])
	by inner-relay-1.corp.adobe.com (8.11.4/8.11.4) with ESMTP id f7F0UB228392
	for <ietf-fax@imc.org>; Tue, 14 Aug 2001 17:30:11 -0700 (PDT)
Received: from [153.32.51.29] ([153.32.51.29]) by
          mailsj-v1.corp.adobe.com (Netscape Messaging Server 4.15 v1 Jul
          11 2001 16:32:57) with ESMTP id GI32PW00.2FQ; Tue, 14 Aug 2001
          17:29:56 -0700 
Mime-Version: 1.0
X-Sender: sfoshee@mailsj-v1.corp.adobe.com
Message-Id: <p04320410b79f6f79904b@[153.32.51.29]>
X-Priority: 1 (Highest)
Date: Tue, 14 Aug 2001 17:25:03 -0700
To: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>,
        "'IETF - fax WG dl'" <ietf-fax@imc.org>,
        "'IETF - John Klensin (IAB Chair)'" <klensin@jck.com>
From: Scott Foshee <sfoshee@Adobe.COM>
Subject: Fwd: IFX> FW: notes from the ietf FAX wg meeting at IETF 51
Cc: "'PWG - IPPFax DL'" <ifx@pwg.org>
Content-Type: multipart/mixed; boundary="============_-1214287258==_============"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


--============_-1214287258==_============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Greetings all....

Claudio and Tamura-san,

I concur with Lloyd that you and Graham did an excellent job of 
capturing the meeting notes in their origional form.

However, I must disagree with Lloyd's proposed revisions on numerous 
points.  I do not think it is in the best interests of the working 
group for us to re-hash the discussion under the guise of accurately 
capturing the meeting notes.  I recommend we go with Graham's and 
Claudio's original notes.  If this can not be supported, then I will 
need to offer comments and counter proposals to almost all of Lloyd's 
comments.  I do not feel his comments capture the neutral spirit of 
Graham's and Claudio's comments.

Please let me know how you wish to proceed on this.

Scott

(Also, please note that I have chosen to include the IEEE IPP group 
in the discussion prior to the Internet Fax committee publishing the 
minutes because Lloyd included them in the discussion.)



>From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
>To: "'IETF - fax WG dl'" <ietf-fax@imc.org>,
>    "'IETF - John Klensin (IAB Chair)'" <klensin@jck.com>
>Cc: "'PWG - IPPFax DL'" <ifx@pwg.org>
>Subject: IFX> FW: notes from the ietf FAX wg meeting at IETF 51
>Date: Tue, 14 Aug 2001 16:14:51 -0700
>Importance: high
>X-Priority: 1
>X-Security: MIME headers sanitized on smtp-relay-2
>	See http://www.impsec.org/email-tools/procmail-security.html
>	for details. $Revision: 1.129 $Date: 2001-04-14 20:20:43-07
>Sender: owner-ifx@pwg.org
>
>Claudio and Tamura-san
>My thanks to you and Graham for the excellent job in capturing the meeting
>proceedings and result.
>Please allow me to suggest a few clarifications below.
>
>Regards,
>Lloyd
>
>>  -----Original Message-----
>>  From: Claudio Allocchio [mailto:Claudio.Allocchio@garr.it]
>>  Sent: Thursday, August 09, 2001 9:26 AM
>>  To: ietf-fax@imc.org
>>  Cc: klensin@jck.com
>>  Subject: notes from the ietf FAX wg meeting at IETF 51
>>
>>
>>
>---snip---
>>
>>   2.2 TIFF-FX
>>        draft-ietf-fax-tiff-fx-09.txt
>>        draft-ietf-fax-tiff-regbis-02.txt
>>
>---snip---
>>  The question now is: can we meet all these constrains? Is TIFF the right
>>  choice to accomplish them?
>The second sentence was not an issued raised by the IAB chair, in fact one
>individual raised this issue. Please consider deleting the second sentence
>or revising to read as follows:
>"The question now is: can we meet all these constrains? One individual asked
>whether TIFF was the right choice to accomplish them?"
>
>>  Basic TIFF does not support colors, and different resolutions, but is it
>>  compliant with the existing TIFF readers, and e-mail User Agents (MUAs).
>Reverse the order of "is it" to read "it is".
>
>>  However, if we want to cover also the "extensions" that ITU-T is
>>  requesting for fax service (e.g. colors, resolutions, etc...) Basic TIFF
>>  is not enough, and it will need extensions.
>Given that accommodation of ITU-T color and higher quality encodings was a
>component of the WG charter, this sentence may be reworded to convey less of
>an impression that it was an afterthought. Please consider the following
>revision:
>"Basic TIFF was not enough to accommodate color and higher quality ITU-T
>encodings, consequently extensions were needed."
>
>>                                                 These extensions were
>>  specified into TIFF-FX, and ITU-T decided to adopt and reference it.
>For completeness, please append "for their Internet Fax standard" to this
>sentence. It should now read:
>"These extensions were specified into TIFF-FX, and ITU-T decided to adopt
>and reference it for their Internet Fax standard."
>
>>  However TIFF-FX is already beyond Basic TIFF.
>>
>>  Actually there are already de facto extensions to basic TIFF
>>  specifications which are publicly available, and widely
>>  deployed within
>  > both TIFF readers and MUAs. All there de facto extensions are
>>  currently
>>  used in MIME type "image/tiff" and there are not interoperability
>>  problems.
>The statement of no interoperability problems with all the de facto
>extensions is inaccurate, since some deployed viewers will not read all the
>extensions. Please reword the second sentence similar to the following:
>"All the de facto extensions are currently used in MIME type "image/tiff"
>and some have no interoperability problems."
>
>>           However the extensions intriduced into TIFF-FX are a superset,
>>  and thus only some Ifax devices can correctly handle them.
>A correction and softening is warranted, given that it is not only Ifax
>devices that are capable of reading TIFF-FX files and the limited
>readability is not an unusual issue with new extensions in general. Consider
>the following:
>"The extensions introduced into TIFF-FX are a superset, which are viewable
>by a limited set of Ifax devices and software applications."
>
>It is important to convey the fact that the WG took deliberate steps to
>avoid incompatibility resulting from addition of new encodings by redefining
>the image/tiff MIME type (i.e. RFC2302) to include an application parameter.
>The results were not quite satisfactory, however, the issue was addressed
>and steps were taken. Accordingly, please consider insertion of the
>following paragraph:
>
>"To avoid interoperability issues arising from introduction of the extended
>color and high quality super set, the image/tiff MIME type was revised to
>add application parameters. The image/tiff application parameters serve to
>alert viewers to the presence of the TIFF-FX superset. Recent disclosures,
>however, indicate that many readers do not pay attention to MIME application
>parameters. It is the inconsistent usage of application parameters that is
>at the heart of TIFF-FX incompatibility with image/tiff viewers."
>
>>
>>  So, the IESG and IAB would like the WG to review and
>>  document, as a condition
>>  for advancing the TIFF specification to Draft Standard:
>>
>>   - Whether the choice of "interoperation with e-mail" versus
>>  "interoperation
>>     with fax" is the right one
>>   - whether a mostly-fax-only TIFF variation is the right choice
>>   - Whether this should be image/tiff or image/tifffx (or equivalent)
>Clarify as follows:
>  "- Whether the MIME sub-type should be image/tiff or image/tifffx (or
>equivalent)"
>
>>   - hether the interoperability profile is right given these issues
>Please clarify, I do not understand what is being said?
>
>>   - and any other similar tradeoffs that might have been made
>>  without full
>>     evaluation.
>
>---snip---
>The paragraph below appears to be lacking context of what the IPR issue is,
>please prefix it with the following:
>"In December 2000 Adobe provided notification of its believe that the
>TIFF-FX specification exceeds the scope of its 1997 IETF license grant for
>TIFF-FX development <http://www.ietf.org/ietf/IPR/Adobe-TIFF>. Inclusion of
>the extended encodings within TIFF-FX was identified as reason for the claim
>of exceeded scope. The validity of this claim has been questioned, given
>that the grant contains no constraint on extensions within TIFF-FX. The fact
>that Abode co-authored both the TIFF-FX and the revised MIME image/tiff
>specifications makes it more difficult to understand the claim.
>Additionally, it may be said that the claim is somewhat late, given that
>TIFF-FX was issued as Proposed Standard in December 1998." 
>
>>  Adobe:  the solution appears to be to have Adobe include the
>>  new TIFF-FX
>>  encodings in TIFF-7, but Adobe has not committed to produce
>>  TIFF-7 and It
>>  is not clear what produces that commitment. Moreover, even if they do
>>  TIFF-7, they will not commit to including the TIFF-FX
>>  features until at
>>  least Xerox releases rights to the encoding techniques for all uses of
>>  TIFF, not just fax and Xerox (or maybe IETF) apply formally
>>  to Adobe to
>>  have the features and tags included. At last, but not the
>>  least, no one at
>>  this IETF can commit Adobe.
>In light of the attached license statement, which clearly states that Xerox
>grants MRC license use within TIFF-FX and without any application space
>restrictions, please correct the 2nd sentence by inserting "MRC" between
>"the encoding" and changing "not just fax and Xerox (or maybe IETF) apply"
>to "not just TIFF-FX, and apply". The sentence should now read:
>"Moreover, even if they do TIFF-7, they will not commit to including the
>TIFF-FX features until at least Xerox releases rights to the MRC encoding
>techniques for all uses of TIFF, not just TIFF-FX, and apply formally to
>Adobe to have the features and tags included."
>
>>
>>  Xerox: Xerox is willing to release rights for all uses in
>>  TIFF if Adobe
>>  will adopt them and include them in TIFF-7. But no one here can commit
>>  Xerox either.
>>
>>  Thus it seems a viable solution currently in a deadlock waiting for
>>  somebody to make the first move.
>>
>---snip---
>>
>>  The discussion of the problem and the WG conclusions.
>>  -------------------------------------------------
>>
>Consider constraining this section to only WG conclusions and procedures to
>be followed, removing the detailed he said/she said commentary. This
>translates to deleting all items prior to the paragraph that starts "Claudio
>A. summarised the conclusions to be reported into the minues,".
>The revised title might read as follows:
>"WG meeting conclusions and procedures to be followed"
>  ----------------------------------------------------
>
>This would be followed by a restructured, consolidated and clarified body as
>below.
>
>A summary of the meeting's rough consensus, along with the procedures to be
>followed, is provided below with "rc" identifying rough consensus items and
>"p" identifying procedure items:
>rc - Interoperability with email was considered the most important choice
>between email or fax interoperability.
>
>p  - Level of interoperability should be established by conducting a test of
>RFC2301 (more appropriately draft-ietf-fax-tiff-fx-09.txt) using existing
>mail user agents (MUAs) and tiff capable software applications such as
>PhotoShop and other tiff viewers. The software viewer test may be
>accommodated by saving the RFC2301 image/tiff stream to a file with .tif or
>other appropriate tiff extension.
>
>p  - An interoperability report should be generated and used to document the
>set of interoperable TIFF-FX encoding parameters, such as coder, resolution,
>paper size and color components.
>
>p  - One of the four options below should be selected for the
>specification(s) that will move forward through the standards tack process:
>      1. Full TIFF-FX: - retain the currently defined TIFF-FX draft without
>modification of the encoding set and define both a new MIME type (e.g.
>image/tifffx or image/tifx) and a new file extension (e.g. .tifx or .tfx).
>The new MIME type and extension circumvents interoperability issues with
>TIFF 6.0.
>         Advantages: i) Retention of color and high quality encodings, ii) no
>disruption of IFax products under deployment, and iii) a single integrated
>specification.
>         Disadvantages: i) Licensing issues to be resolved, and ii)
>unpredictable approval schedule due to license resolution.
>
>      2. Interoperable TIFF-FX: - use the new interoperability document to
>generate a TIFF-FX subset that is image/tiff interoperable, retaining the
>current image/tiff MIME type.
>         Advantages: i) No licensing issues, and ii) predictable approval
>schedule.
>         Disadvantages: i) Loss of color and high quality encodings, ii)
>disruption of IFax products under deployment.
>
>      3. Interoperable and non-Interoperable TIFF-FX: - use the new
>interoperability document to generate two subsets, a) Interoperable TIFF-FX,
>as per #2, and b) non-Interoperable TIFF-FX, which is composed of the
>remaining encoding subset. As with Full TIFF-FX, define both a new MIME type
>and a new file extension for the non-Interoperable TIFF-FX.
>         Advantages: i) Base-level black-and-white has no licensing issues,
>ii) predictable base-level approval schedule iii) retention of color and
>high quality encodings, iv) minimal disruption of IFax products under
>deployment.
>         Disadvantages: i) Licensing issues to be resolved for color & high
>quality, ii) unpredictable color & high quality approval schedule, iii) two
>disjoined specifications.
>
>      4. Interoperable and Full TIFF-FX: - this is a combination of options 1
>and 2.
>         Advantages: i) Base-level black-and-white has no licensing issues,
>ii) predictable base-level approval schedule iii) retention of color and
>high quality encodings, iv) no disruption of IFax products under deployment,
>and v) base-level specification may be phased out as viewers advance.
>         Disadvantages: i) Licensing issues to be resolved for color & high
>quality, ii) unpredictable color & high quality approval schedule.
>
>rc - Option 2, Interoperable TIFF-FX, was selected to move forward at this
>time.
>
>p  - Justification of the selection must be documented and communicated to
>the ITU.
>
>p  - Both the resulting specification and the Implementors Guide should
>contain explanation of the interoperability issues and countermeasures.
>
>p  - The resulting specification(s) may be resubmitted to the IESG for Draft
>Standard consideration if there are draft-ietf-fax-tiff-fx-09.txt
>function/feature deletions or no changes. This means that Full TIFF-FX, with
>no changes, and both the Interoperable TIFF-FX and non-Interoperable TIFF-FX
>subsets, without any additions, may be resubmitted to the IESG for Draft
>Standard consideration. Any required specification additions shall result in
>recycle as Proposed Standard.
>
>p  - Resolution of IPR issues associated with Full TIFF-FX and
>non-Interoperable TIFF-FX needs to progress in parallel with the above
>activates and the ITU should be kept informed.
>
>---snip---
>
>>  5.5 TIFF-FX extension issue
>>       draft-ietf-fax-tiff-fx-Extension-1-02.txt
>>       (drtyre-tiff-fx-extension1-02.txt)
>>      darft-mcintyre-feature-schema-extension1-00.txt
>
>>  After remembering that all the issues in these documents are related to
>>  the previous discussion about TIFF and TIFF-FX issue, and that IPR
>>problems should be clearly investigated also for these proposed
>>  extensions, the presentation (see slies) described the further JBIG2
>>  extensions.
>
>>  Larry M. asked how many in the room read the draft:  One person. As such
>>  the question was raised if we should continue the work, if there is
>>  interest in doing it or not, provided that at a certain point the
>>  specification will have to undego interoperability tests, and the lack of
>>  interest could lead to a lack of implementations.  There was at the moment
>>  no conclusion to ths question, as we need to check first the status of the
>>  TIFF issue evolution.
>The second paragraph should be depersonalized and clarified to note that
>there was confusion as to which specification was being addressed by the
>question of number of reviewers. The question was asked toward the end of
>the Schema, not the TIFF-FX Extension presentation. The respondent was a
>reviewer of the Schema extension, which is a very new draft with little time
>for review. Revise as follows:
>"Toward the end of the Schema extension presentation a member ask how many
>had read the draft, there was no clarifications as which draft was being
>referenced. There was acknowledgement from on member who had reviewed the
>Schema drat. The requestor then asked whether the work should be continued,
>without much response. No conclusions could be drawn."
>
>

--============_-1214287258==_============
Content-Id: <p04320410b79f6f79904b@[153.32.51.29].0.0>
Content-Type: multipart/appledouble; boundary="============_-1214287258==_D============"

--============_-1214287258==_D============
Content-Type: application/applefile; name="%Xerox_IETF_IPR_statement.txt"
Content-Disposition: attachment; filename="%Xerox_IETF_IPR_statement.txt"
 ; modification-date="Tue, 14 Aug 2001 17:01:32 -0700"
Content-Transfer-Encoding: base64

AAUWBwACAAAAAAAAAAAAAAAAAAAAAAAAAAMAAAADAAAAPgAAABwAAAAJAAAAWgAAACAA
AAAIAAAAegAAABBYZXJveCBJRVRGIElQUiBzdGF0ZW1lbnQudHh0VEVYVHR0eHQAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAADDBXsAwwV7EttDAADDBv2
--============_-1214287258==_D============
Content-Type: text/plain; name="Xerox_IETF_IPR_statement.txt"; charset="us-ascii"
Content-Disposition: attachment; filename="Xerox_IETF_IPR_statement.txt"
 ; modification-date="Tue, 14 Aug 2001 17:01:32 -0700"


From http://www.ietf.org/ietf/IPR/XEROX-RFC2301

The following was conveyed via email on September 9, 1999 by Clarke Wixon
Patent Attorney, Xerox


Mr. Stephen Coya
Executive Director
Internet Engineering Task Force
c/o Corporation for National Research Initiatives
1895 Preston White Drive, Suite 100
Reston, Virginia 20191-5434

Re:     IETF RFC 2301 (TIFF-FX) IPR Statement

Dear Mr. Coya:

Xerox is currently aware of two U.S. Patents which may relate to implementations of
the IETF RFC 2301 (TIFF-FX) standard. U.S. Patent No. Re35,657 is owned by Xerox
Corporation. U.S. Patent No. 5,778,092 is owned by ScanSoft, Inc., but Xerox has
rights to sublicense the technology for these purposes.

To the extent that Xerox's existing intellectual property rights under the above two
patents may cover the implementation of a product compliant with the TIFF-FX
standard, Xerox agrees to provide, upon request, a royalty-free, world-wide,
non-exclusive license under certain claims of the above two patents (not including
the segmentation technology described in the specification and set forth in claims
2-4, 7, 8, or 12-14 of U.S. Patent No. 5,778,092, which is not considered to be an
essential technology for the implementation of the TIFF-FX standard) for the purpose
of making, having made, using, selling, offering for sale, or otherwise disposing of
a product implementing the TIFF-FX standard, and only to the limited extent
necessary for the product to comply with the TIFF-FX standard.

Any license granted by Xerox under this Statement shall be subject to the following
condition: any party receiving such a grant from Xerox must agree to grant Xerox
Corporation, Xerox Ltd., Fuji Xerox Co. Ltd., Modi Xerox Limited and any
corporation, firm, partnership, individual, or other form of business organization
at least forty percent (40%) owned or controlled, directly or indirectly, by Xerox
Corporation, Xerox Ltd., Fuji Xerox Ltd. or Modi Xerox Limited, upon request, a
license under that party's patents relating to the TIFF-FX standard, on terms and
conditions no less favorable than those granted by Xerox to that party.

Parties interested in obtaining a license may contact:

Xerox Intellectual Property Operations (XIPO)
ATTN: MRC License Inquiries
100 Willowbrook Office Park, Bldg. 832-01A
Fairport, New York 14450  U.S.A.

Very truly yours,

/s/

Dr. Jan Jaferian
Vice President

c:      James Rafferty (IFax WG Chair) <jrafferty@worldnet.att.net>
        Keith Moore (IETF Area Director) <moore@cs.utk.edu>
        Patrik Faltstrom (IETF Area Director) <paf@swip.net>


Clarke Wixon
Patent Attorney
Xerox Corporation


--============_-1214287258==_D============--
--============_-1214287258==_============--


From owner-ietf-fax@mail.imc.org  Tue Aug 14 21:30:16 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19141
	for <fax-archive@odin.ietf.org>; Tue, 14 Aug 2001 21:30:15 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7F0oBb02760
	for ietf-fax-bks; Tue, 14 Aug 2001 17:50:11 -0700 (PDT)
Received: from iscan.toyocom.co.jp (mail.toyocom.co.jp [210.232.21.1])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7F0o8N02754
	for <ietf-fax@imc.org>; Tue, 14 Aug 2001 17:50:09 -0700 (PDT)
Received: from iscan.toyocom.co.jp (localhost [127.0.0.1])
	by iscan.toyocom.co.jp (8.9.3+3.2W/3.7W) with ESMTP id JAA01644
	for <ietf-fax@imc.org>; Wed, 15 Aug 2001 09:49:12 +0900
Received: from smtp.toyocom.co.jp (smtp.toyocom.co.jp [10.1.11.24])
	by iscan.toyocom.co.jp (8.9.3+3.2W/3.7W) with ESMTP id JAA01596;
	Wed, 15 Aug 2001 09:49:09 +0900
Received: from toyocom.co.jp ([172.16.72.36])
	by smtp.toyocom.co.jp (8.9.3+3.2W/3.7W) with ESMTP id JAA07546;
	Wed, 15 Aug 2001 09:56:39 +0900
Message-ID: <3B79C83A.7030507@toyocom.co.jp>
Date: Wed, 15 Aug 2001 09:54:18 +0900
From: Katsuhiko Mimura <mimu@toyocom.co.jp>
Organization: TOYOCOM Network Systems
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; ja-JP; m18) Gecko/20010131 Netscape6/6.01
X-Accept-Language: ja, en-us
MIME-Version: 1.0
To: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
CC: Claudio.Allocchio@garr.it, ietf-fax@imc.org
Subject: Re: notes from the ietf FAX wg meeting at IETF 51
References: <Pine.VMS.3.91-B.1010809170453.46409A-100000@SYNX02.elettra.trieste.it> <20010810055244R.adm@ifax.attnet.ne.jp>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Tamura-san,

Hiroshi Tamura wrote:


> I remember that there was a comment about it.
> If my understanding is correct, updating the new ones are not necessary
> at that time for the WG LCs. Am I right?
<snip>
> Mimura-san,
> Do you modify your I-D as the above suggestion?
 
Yes, we would like to use "could be" instead of "is".
and we will update the I-Ds soon.

/Mimura




From owner-ietf-fax@mail.imc.org  Tue Aug 14 22:02:00 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20356
	for <fax-archive@odin.ietf.org>; Tue, 14 Aug 2001 22:01:59 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7F1LaS03722
	for ietf-fax-bks; Tue, 14 Aug 2001 18:21:36 -0700 (PDT)
Received: from chmls06.mediaone.net (chmls06.mediaone.net [24.147.1.144])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7F1LYN03718
	for <ietf-fax@imc.org>; Tue, 14 Aug 2001 18:21:34 -0700 (PDT)
Received: from solo120.humancomm.com (h0080c88ffcc6.ne.mediaone.net [66.30.186.202])
	by chmls06.mediaone.net (8.11.1/8.11.1) with ESMTP id f7F1LNm15377
	for <ietf-fax@imc.org>; Tue, 14 Aug 2001 21:21:24 -0400 (EDT)
Message-Id: <5.0.2.1.2.20010814211556.03d7b980@humancomm.com>
X-Sender: jrafferty@humancomm.com
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 14 Aug 2001 21:16:25 -0400
To: Ietf-Fax <ietf-fax@imc.org>
From: James Rafferty <jrafferty@humancomm.com>
Subject: Re: FW: notes from the ietf FAX wg meeting at IETF 51
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by above.proper.com id f7F1LZN03719
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit


To all -

I have some comments on the TIFF-FX portion of the
IETF minutes as reported by Claudio Allocchio.

My comments are not regarding the accuracy of
the meeting coverage, but rather on the portrayal of
what took place when Adobe submitted its license
letter for TIFF and the concurrent process which led
to standardization of RFC 2301.

I have serious concerns about what appears to
be an effort by some to re-write history
or to reverse decisions previous made witin the WG.   My opinions
here are my own, based on my experiences as
WG co-chair and RFC 2301 contributor during the time in question.

My advance apologies for the length of the message, but
there were several issues raised and my comments
are in response to them.
 > -----Original Message-----
> > From: Claudio Allocchio [mailto:Claudio.Allocchio@garr.it]
> > Sent: Thursday, August 09, 2001 12:26 PM
> > To: ietf-fax@imc.org
> > Cc: klensin@jck.com
> > Subject: notes from the ietf FAX wg meeting at IETF 51
> >

<snip>


> > Short notes of the ietf FAX WG meeting - IETF 51 London, UK
> > ------------------------------------------------------
> >
<snip>


> >  2.2 TIFF-FX
> >       draft-ietf-fax-tiff-fx-09.txt
> >       draft-ietf-fax-tiff-regbis-02.txt
> >
> > The documents approval is slowed down by a series of problems
> > which were
> > detected during the process. ITU-T also needs a quick
> > resolution of there
> > problems as stated in the communication letter from ITU-T
> > SG16 meeting.
> >
> > The problem, detected at first as an IPR issue raised by
> > Adobe in January
> > 2001, was escalated to IESG and IAB which examined carefully
> > all the aspects,
> > and identified also some additional compatibility issues.
> >
> > John Klensin (IAB) reported to the WG.
> >
> > The TIFF Story, actually had many different steps and
> > chapters. During the
> > analysis of the problem there were many iterations between
> > the IESG and
> > the IAB which at the end pointed out two Separate Issues:
> >
> >  - WG responsibility for interoperability
> >  - IPR questions
> >
> > At first the interoperability. This is the "Main IETF Goal" to be
> > achieved, and its meaning should span forward and sideways. The main
> > principles are that:
> >
> >  - Implementations of one protocol must interoperate
> > Ð- Implementations of related protocols should interoperate
> > Ð- Deviations must make sense and have a clear rationale behind.
> >
> > In its original goals (and as stated in the charter) the fax wg had to
> > create a Fax Model that should Interoperate with fax fabric and
> > Interoperate with e-mail fabric. More over it should avoid having to
> > choose between the two fabrics. For this reason TIFF was
> > chosen because It
> > was widely believed that it would be interoperable with
> > existing viewers
> > and editors, especially Viewers expected to be used with image/tiff in
> > e-mail. This shoud also be the start of the "global messaging
> > service".
> >
> > The question now is: can we meet all these constrains? Is
> > TIFF the right
> > choice to accomplish them?
> >
This is a gross oversimplification of the compatibility
issues and ignores the substantial use of TIFF-F
by the computer fax community, which uses
products such as fax boards and fax modems in
association with TIFF-F implementations.   So,
the interoperability issues which were being
addressed when TIFF was considered by the WG and
eventually chosen were to focus on the current
uses of TIFF by both the fax community and the
email community.    This current use of TIFF
had a great deal of influence on the drafting
of the TIFF-F and later TIFF-S sections
of what became RFC 2301.   Steve Zilles
of Adobe was actively involved in these
discussions both on the list and in
small editing groups.

> > Basic TIFF does not support colors, and different
> > resolutions, but is it
> > compliant with the existing TIFF readers, and e-mail User
> > Agents (MUAs).
> > However, if we want to cover also the "extensions" that ITU-T is
> > requesting for fax service (e.g. colors, resolutions, etc...)
> > Basic TIFF
> > is not enough, and it will need extensions. These extensions were
> > specified into TIFF-FX, and ITU-T decided to adopt and reference it.
> > However TIFF-FX is already beyond Basic TIFF.
> >
I will note that TIFF-F is NOT the same as Baseline TIFF (since
Baseline TIFF makes no use of compression and is therefore
unsuitable for transport of facsimile).  However, the TIFF 6.0
spec also goes beyond baseline TIFF and DOES include
tags that can represent the compressions used in pre-1996
fax (i.e MH, MR and MMR).   It was clear from our
discussions with implementors when RFC 2301 was being
drafted that many conventional TIFF viewers as implemented
could typically handle both the Baseline TIFF and TIFF-F
extensions.

> > Actually there are already de facto extensions to basic TIFF
> > specifications which are publicly available, and widely
> > deployed within
> > both TIFF readers and MUAs. All there de facto extensions are
> > currently
> > used in MIME type "image/tiff" and there are not interoperability
> > problems.
Well, actually, at the direct request of Steve Zilles, the RFC 2301
content shows exactly how TIFF-F is derived from TIFF 6.0
and is therefore fully consistent with the Adobe license letter.
So, its not merely "de facto" extensions, and yes, there
are no substantive interoperability problems.   In fact, some
implementors told me after RFC 2301 was published that
the text had gone a long way to resolve and reconcile some of the
different interpretations that had been made of Joe Campbell's
TIFF-F documents that were published in the early 90's.


>However the extensions intriduced into TIFF-FX are
> > a superset,
> > and thus only some Ifax devices can correctly handle them.
> >
Well, yes, there are extensions.  However, if Ifax devices
and TIFF implementations follow the rules of TIFF 6.0 and RFC 2301, they 
will ignore
tags they do not understand.   If they do not do this,
they have broken the rules, which we cannot prevent.

> > So, the IESG and IAB would like the WG to review and
> > document, as a condition
> > for advancing the TIFF specification to Draft Standard:
> >
> >  - Whether the choice of "interoperation with e-mail" versus
> > "interoperation
> >    with fax" is the right one
> >  - whether a mostly-fax-only TIFF variation is the right choice
> >  - Whether this should be image/tiff or image/tifffx (or equivalent)
> >  - hether the interoperability profile is right given these issues
> >  - and any other similar tradeoffs that might have been made
> > without full
> >    evaluation.
> >
Well, excuse me, but we did a full evaluation of all of these
options during the long, drawn out (1 year) standardization process
for RFC 2301.  All members of the WG had a chance
to participate and Adobe and Xerox both
had people who were among the RFC 2301 authors.
The ITU-T also had substantial discussion of these issues
prior to agreeing that they wanted to reference RFC 2301
for T.37.

> > The IAB believes now it is late in the game, so these reviews may not
> > change anything, but they are important for learning, and context, and
> > predicting problem areas and determining whether the
> > meta-qualifications
> > for Draft Standard are met.
> >
There was substantial additional work done on RFC 2301 interoperability
at 2 public Fax Connect interop events and in other activities.
The results of these activities have been reported to the WG
and the IESG.   Why is this now being questioned?

> > John Klensin then reported on the IPR issues, which invove
> > both Adobe and
> > Xerox.
> >
> > Adobe:  the solution appears to be to have Adobe include the
> > new TIFF-FX
> > encodings in TIFF-7, but Adobe has not committed to produce
> > TIFF-7 and It
> > is not clear what produces that commitment. Moreover, even if they do
> > TIFF-7, they will not commit to including the TIFF-FX
> > features until at
> > least Xerox releases rights to the encoding techniques for all uses of
> > TIFF, not just fax and Xerox (or maybe IETF) apply formally
> > to Adobe to
> > have the features and tags included. At last, but not the
> > least, no one at
> > this IETF can commit Adobe.
> >
Briefly, when Adobe submitted their license letter to the IETF and
the ITU-T,  there was only 1 proposal on the table for standardization,
the TIFF-FX draft which later became RFC 2301.   Given
that Steve Zilles was both a WG member and TIFF-FX
co-author, my basic interpretation at that time as co-chair was
that Adobe was giving the IETF the go-ahead to produce
the TIFF extensions being addressed in RFC 2301.  No
mention was made of any dependencies on "TIFF 7",
which IS NOT referenced in RFC 2301, since the
document uses TIFF 6.0 and then clearly indicates
which extensions go beyond fields defined in TIFF 6.0.

I might add that Steve Zilles was a strong advocate
in the WG for
producing a TIFF-FX document which included
both TIFF-F content AND the profiles which went
beyond TIFF-F.

> > Xerox: Xerox is willing to release rights for all uses in
> > TIFF if Adobe
> > will adopt them and include them in TIFF-7. But no one here can commit
> > Xerox either.
> >
> > Thus it seems a viable solution currently in a deadlock waiting for
> > somebody to make the first move.
> >
> > At last, we have the ITU issue, who is referencing our
> > documents. But ITU
> > approach to IPR is different, and a licence issued to the
> > IETF might not
> > fully apply also to ITU. There is a strict need to coordinate with ITU
> > also on these IPR matters, to avoid future problems. It is in
> > fact clear
> > that what was released to IETF is not automatically released
> > to ITU (and
> > viceversa).
> >
This is a red herring IMHO.   The ITU-T received a letter from
Adobe which is basically identical to that received by
the IETF; so the IPR issue was dealt with independently
in accordance with the rules of both groups.    ITU-T participants
may recall that there was a great deal of attention paid
to procedural matters during this unprecedented first direct
collaboration of the IETF and the ITU-T, before RFC 2301
and the other IETF RFCs were referenced by T.37.   .


> > The discussion of the problem and the WG conclusions.
> > -------------------------------------------------
> >
> > The original reasons for using TIFF were lightweight,
> > extensibility and
> > its ITU compatibility, and it ability to be understood as a MIME type
> > image/tiff by most of the MUAs.
> >
> > The extensions are actually needed to meet the new specification which
> > ITU-T had done, but the new extensions also introduce
> > impatibility and IPR
> > possible clashes.
> >
> > Dave Crocker suggest as a first prroximation solution to skim down the
> > core specification to a "safe" subset, and pursue the other issues
> > separately, with a separate MIME type.
> >
Well, this solution was proposed several times during the RFC 2301
standardization, but not supported by the WG, so RFC 2301
went ahead with support for the 6 profiles.    Is there
now a consensus to reverse the previous direction???

> > Scott Forshee suggested also that other focus has been on JPEG-2000
> > specifications , and work is progressing on a different (planned) MIME
> > type including MRC capabilities.  However igher level features of
> > JPEG-2000 are generally not widely deployed. He proposed the wg to
> > reconsider JPEG-2000 as an alternate to TIFF-FX. Moreover, part of the
> > reason for Adobe's objections are to keep the use of TIFF freely
> > available.
> >
> > There were objections to this proposal, stating the JPEG-2000
> > is not yet
> > in good shape, has not yet a MIME type registered, too, and its wide
> > deployment is not existing at the moment.
> >
Well, but of course.  This is not an acceptable solution.


> > A discussion followed, considering if one should simply use
> > the version
> > label into MIME typ definition to define which level of TIFF is being
> > used, or just a totally new type.
> >
> > Claudio Allocchio suggested that image/tiff should be used
> > onlyfor minimum
> > interoperable features and anything else should have a
> > different name and
> > label; this will have to happen for TIFF-7 in any case.
> >
> > Lloyd McIntyre suggested as simple solution to revert to previously
> > registered version of TIFF, i.e. TIFF 6.0, excluding also any widely
> > deployed de facto extensions. There was a discussion on this,
> > and Scott F.
> > stated that TIFF 6.0 was issued in 1992, with updates via by technical
> > notes, which are widely implemented.  Thus RFC 2302 is OK with the way
> > that Adobe and others use TIFF. We should focus on the
> > TIFF-FX spec, to
> > cut it back to non-controversial features.
> >
> > At this point Claudio A. asked the wg members present at the
> > meeting if
> > anyone strongly oppose the approach proposed by Dave C.?
> >

<snip>

> >
> > The wg expressed consensus on the above approach. This
> > consensus need to be
> > confirmed by the mailing list.
> >
I will look forward to the discussion of this proposal on the mailing
list, where the decision needs to be made.

> > Claudio A. summarised the conclusions to be reported into the
> > minues, and to
> > facilitate the understanding of the approach by anybody
> > including those not
> > present at the meeting:
> >
> >   - we must consider for interoperability test of RFC2301
> > also existing
> >     mail user agents (MUAs), and they should be able to read
> > image/tiff
> >     bodyparts generated bu Ifax devices. Interoperability is
> > the choice.
> >
If they are broken and cannot ignore tags that they do not
understand, that is not the problem of the IETF.
> >   - we must also consider interoperability with existing tiff capable
> >     software, e.g. saving the image/tiff to a file and
> > reading it with ...
> >     Photoshop, and other tiff files readers.
> >
I think the most relevant set is the readers used by the
fax and email communities, since this is the focus
of Internet fax.   There are all kinds of other TIFF
uses which are irrelevant to this discussion.


> >  - we should produce a new interoperability report, and based on this
> >    we should detail the revision of RFC2301, to fit any feature which
> >    proved to interoperate in all above cases, even if not included in
> >    basic TIFF 6.0 specification.
> >
> >  - thus existing tiff-fx Ifax devices go beyond this, as they
> > my generate
> >    extensions which do not interoperate correctly with the above
> >
We cannot turn back the clock and pretend that the many TIFF-F
implementations of the past 10 years do not exist, nor is
it acceptable to ignore the many Ifax implementations
which use the TIFF-S subset of TIFF-F.   The
practical baseline for implementations is to support TIFF 6
and at least up to the RFC 2301 TIFF-F profile.   The
existing interop work focused heavily on these areas,
with a smaller number of implementors supporting
the other RFC 2301 profiles which had additional extensions.
BTW, those extensions did not materialize out of
nowhere, but were precisely put together to provide
interoperability with the huge G3 install base
and the T.30 extensions approved during the 1990's which
have added support for JBIG-1, JPEG and, more recently,
MRC.   The ITU-T work preceded the IETF work and
was referenced by RFC 2301.

> >  - thus we should define how to create a NEW format (both for
> > files and
> >    for MIME readers) with a different name which may be
> > tiff-fx, or totally
> >    different, to make clear to implementers and devices that
> > "this is an
> >    extended new format" (even if based on tiff in origin).
> >
> >  - the reason for removing from RFC2301 revision some features is
> >    because they do not interoperate on the global service,
> > even if they
> >    proved to interoperate among Ifax implementaions.
> >
Whoa!  I have big problems with this.   There is a broad community
of TIFF implementors, including the Ifax implementors.   If the
Ifax implementations interoperate AND also interoperate
with common fax community use of TIFF, this does meet
the needs for interoperation within the IETF community IMO.

> >  - the "recuded set" specification will be submitted for
> > Draft Standard
> >
> >  - we should, at the same time, produce a new "extended specification"
> >    docuement, which includes the extensions existing in RFC2301 and
> >    dropped in the Draft Standard document, and might also include the
> >    further extensions proposed for "full mode". This
> > document(s) should
> >    also define a different MIME type registration for this extended
> >    specification. This new specification should go as
> > Proposed Standard
> >
> >  - we need to investigate if it is possible to declare
> > RFC1301 "Updated"
> >    by the new Draft Standard document, at least until the new
> > "Proposed
> >    Standard" document obsoletes RFC2301. ADs suggestions are expected.
> >
> >  - we should carefully inform ITU-T of the reasons of this choice.
> >
> >  - the Draft Standard version of the specification would also not have
> >    (apparently) IPR issues related, and the extended mode one should
> >    carefully consider IPR problems while being specified.
> >
If there was an attempt to extract TIFF-F and TIFF-S from the
RFC 2301, assuming that  WG consensus on this action
was demonstrated,
I would see no reason why this subset would not go forward
as a draft standard, based on now many years of implementation
history, which has been documented at various interop events.


<End of Comments>

James Rafferty



From owner-ietf-fax@mail.imc.org  Wed Aug 15 05:34:55 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11370
	for <fax-archive@odin.ietf.org>; Wed, 15 Aug 2001 05:34:54 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7F8pIQ03849
	for ietf-fax-bks; Wed, 15 Aug 2001 01:51:18 -0700 (PDT)
Received: from pp-mx0.tokyo.spin.ad.jp (PP-mx0.Tokyo.Spin.AD.JP [165.76.52.9])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7F8nuN03813
	for <ietf-fax@imc.org>; Wed, 15 Aug 2001 01:49:57 -0700 (PDT)
Received: from localhost (pl073.nas323.sagamihara.nttpc.ne.jp [210.165.205.169]) by pp-mx0.tokyo.spin.ad.jp (8.8.8+Spin/3.6W-JENS-stand2(09/30/00)) id RAA20898; Wed, 15 Aug 2001 17:48:23 +0900 (JST)
To: ietf-fax@imc.org, klensin@jck.com
Subject: TIFF-FX issue
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010815174627T.adm@ifax.attnet.ne.jp>
Date: Wed, 15 Aug 2001 17:46:27 +0900 (JST)
X-Dispatcher: imput version 20000228(IM140)
Lines: 55
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


To all:

Please be calm.

Although I am in holiday, I cannot help but comment.
Claudio and I seem to be in troubles for completing our minutes at London.
Please wait until he comes back.

At first I have say, I cannot comment all of them now, because
I do not have enough time to read all of them CAREFULLY. Sorry.

But, I say some points.

1. There are RFC2301 and RFC2302.
Lots of implementers already have products or something,
according to these RFCs. We cannot change the contents technically.
Therefore, they cannot be obsoleted.
Also, I want to say that ITU-T T.37 refer them. We cannot change them
without ITU-T agreement.

2. Interoperability test, etc.
IAB suggests there is lack of interoperability test with some softwares
handling image/tiff, not IFAX devices. So, the implementation
report by the editors seems not to be enough as it is for Draft Standard
consideration.

Therefore, another content-type is suggested for TIFF-FX.
But, the use of other types might cause the compatibility issues
with the existing RFC2301 and RFC2302 devices and softwares.

3. Adobe was a contributor of RFC2301.
I would like to avoid the comments about it now.
I have to be neutral as a co-chair.

.....

Our meeting minutes is not so important for us. The issue here is
that the realistic solution is needed so that everyone can reach to compromise.

.....

Of course, as one of implementers, I have comments.
As a PERSONAL comment, I would like to keep using
the existing RFC2301 and RFC2301 technically,
irrespective of the level of Standard.

.....

BTW, I am now very busy with my regular work, so,
Please do not expect early response from me.

Regards,
--
Hiroshi Tamura, Co-chair or IETF-FAX WG
tamura@toda.ricoh.co.jp


From owner-ietf-fax@mail.imc.org  Wed Aug 15 18:14:12 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02105
	for <fax-archive@odin.ietf.org>; Wed, 15 Aug 2001 18:14:12 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7FLIRI13122
	for ietf-fax-bks; Wed, 15 Aug 2001 14:18:27 -0700 (PDT)
Received: from pasiphae.eastgw.xerox.com (pasiphae.xerox.com [208.140.33.23])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7FLIBN13110
	for <ietf-fax@imc.org>; Wed, 15 Aug 2001 14:18:25 -0700 (PDT)
Received: from crthub2.crt.xerox.com (crthub2.crt.xerox.com [13.138.80.5])
	by pasiphae.eastgw.xerox.com (8.9.3/8.9.3) with ESMTP id RAA22438;
	Wed, 15 Aug 2001 17:17:57 -0400 (EDT)
Received: by crthub2.crt.xerox.com with Internet Mail Service (5.5.2653.19)
	id <QQP55J5V>; Wed, 15 Aug 2001 17:18:06 -0400
Message-ID: <BF85F885643CD21188230008C7562935032B05C0@crte128-2.wrc.xerox.com>
From: "Buckley, Robert R" <RBuckley@crt.xerox.com>
To: "'Dan Wing'" <dwing@cisco.com>, IETF Internet Fax WG <ietf-fax@imc.org>
Subject: RE: IETF puts brakes on TIFF-FX
Date: Wed, 15 Aug 2001 17:18:07 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


One statement in this article needs correction. It says that Xerox "won't
back TIFF-FX unless Adobe promises to support the standard in its next
version of TIFF, TIFF 7.0." That's news to me and is simply not true--Xerox
already supports 3 TIFF-FX profiles in released Internet Fax products. 

Rob Buckley

-----Original Message-----
From: Dan Wing [mailto:dwing@cisco.com]
Sent: Tuesday, August 14, 2001 12:30 PM
To: IETF Internet Fax WG
Subject: CNN: IETF puts brakes on TIFF-FX



> >ADOBE, XEROX TIFF SLOWS INTERNET FAX STANDARD
> >
> >
> >The Internet Engineering Task Force has slammed the brakes on its plans
to
> >develop a common way of sending faxes over the Internet, due to
> >last-minute licensing problems between rivals Adobe Systems and Xerox.
> >
>
http://www.cnn.com/2001/TECH/internet/08/13/adobe.xerox.tiff.idg/index.html


From owner-ietf-fax@mail.imc.org  Thu Aug 16 06:15:32 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27262
	for <fax-archive@odin.ietf.org>; Thu, 16 Aug 2001 06:15:32 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7G9THE28711
	for ietf-fax-bks; Thu, 16 Aug 2001 02:29:17 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7G9RsN28449
	for <ietf-fax@imc.org>; Thu, 16 Aug 2001 02:27:55 -0700 (PDT)
Received: from azteca.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.74])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id SAA04557;
	Thu, 16 Aug 2001 18:19:38 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by azteca.isd.ricoh.co.jp (Mirapoint)
	with SMTP id AAY02159;
	Thu, 16 Aug 2001 18:19:37 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id SAA09089; Sat, 11 Aug 2001 18:05:39 +0900
To: sfoshee@Adobe.COM, Lloyd.McIntyre@pahv.xerox.com
Cc: ietf-fax@imc.org, klensin@jck.com, ifx@pwg.org
Subject: Re: Fwd: IFX> FW: notes from the ietf FAX wg meeting at IETF 51
In-Reply-To: <p04320410b79f6f79904b@[153.32.51.29]>
References: <p04320410b79f6f79904b@[153.32.51.29]>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010816182313C.tamura@toda.ricoh.co.jp>
Date: Thu, 16 Aug 2001 18:23:13 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 36
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Hello everyone,

I checked some of the mails.

Regarding IETF-FAX WG minutes, it seems that we need to modify it.
I would like to say, "easy to understand" and "simple".

Especially, regarding TIFF-FX issue, I would like to shrink it
as the most important parts are kept. For example, the things that
do not relate to our conclusion at the meeting might be deleted.
Also, what was not discussed at the meeting might be deleted.
Just my idea.

Of course, at first, I need the agreement by Claudio.

Anyway, I would like to confirm our conclusion at the meeting.

1. Safe subset for Draft Standard Consideration
2. Final agreement will be made in this ML.

But, it is lack of information for the people that did not attend
our meeting. Because other choices are not written in the draft minutes.
Fortunately, in the meeting, they were shown, although they were not accepted.
At least, they have to be shown in this ML.

But, please wait for the others. I do not check all the related mails.

Also, please wait for the next version of our draft minutes.

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp





From owner-ietf-fax@mail.imc.org  Sun Aug 19 19:30:44 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17114
	for <fax-archive@odin.ietf.org>; Sun, 19 Aug 2001 19:30:44 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7JMpDM01477
	for ietf-fax-bks; Sun, 19 Aug 2001 15:51:13 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7JMp2N01472
	for <ietf-fax@imc.org>; Sun, 19 Aug 2001 15:51:03 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id HAA12842;
	Mon, 20 Aug 2001 07:44:07 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id ABC81510;
	Mon, 20 Aug 2001 07:44:02 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id HAA07170; Mon, 20 Aug 2001 07:43:59 +0900
To: sfoshee@Adobe.COM, Lloyd.McIntyre@pahv.xerox.com
Cc: ietf-fax@imc.org, klensin@jck.com, ifx@pwg.org
Subject: Re: Fwd: IFX> FW: notes from the ietf FAX wg meeting at IETF 51
In-Reply-To: <20010816182313C.tamura@toda.ricoh.co.jp>
References: <p04320410b79f6f79904b@[153.32.51.29]>
	<20010816182313C.tamura@toda.ricoh.co.jp>
	<51B8ABCE456FD111899900805F6FD6EE067A352A@mercury.ADOC.xerox.com>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010820074741P.tamura@toda.ricoh.co.jp>
Date: Mon, 20 Aug 2001 07:47:41 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 107
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


To all:

I checked Lloyd's suggestions.

I think some of corrections are reasonable because of ambiguity.
Others are not discussed at the meeting. They are considerable options
for TIFF-FX. This should be done from now on.

Claudio and I cannot make our mintues that is completely satisfactory
to both of you. Therefore, please accept it even if there are something
that you have complaint.

I repeat my policy.
> Regarding IETF-FAX WG minutes, it seems that we need to modify it.
> I would like to say, "easy to understand" and "simple".

Anyway, until Claudio comes back, please wait.

The next, I would like to introduce the background.

Some slides at the meeting:
-------------------------------------------------------------------------------

- TIFF extension beyond basic black-and-white induces incompatibility
  with existing base tiff applications
    Should we retreat to only base set black-and-white, retaining full
    compatibility with existing tiff base or continue to embrace the defined
    path that introduces new encodings for both black-and-white and color that
    are consistent with ITU-T fax encodings?

    1 If decision is to retain extended encodings then compatibility must be
      addressed, two options are:
        Different MIME type and file extension
	or
	Different MIME type and file extension  together with a new Adobe
        issued TIFF version that encompass the TIFF-FX encodings

    2 If decision is to retreat to only base black-and-white then we must:
        Delete all TIFF-FX profiles other than S and F with constraints as follows:
        encodings MH, MR and MMR resolutions of 200x100 and 200x200 paper size A4/letter

-------------------------------------------------------------------------------

These are just descriptions. Some of the above may not be appropriate.

I said:
> Anyway, I would like to confirm our conclusion at the meeting.
> 
> 1. Safe subset for Draft Standard Consideration
> 2. Final agreement will be made in this ML.

But, we do not decide precisely what is safe subset.

Lloyd said:
> p  - One of the four options below should be selected for the
> specification(s) that will move forward through the standards tack process:
>      1. Full TIFF-FX: - retain the currently defined TIFF-FX draft without
> modification of the encoding set and define both a new MIME type (e.g.
> image/tifffx or image/tifx) and a new file extension (e.g. .tifx or .tfx).
> The new MIME type and extension circumvents interoperability issues with
> TIFF 6.0. 
>         Advantages: i) Retention of color and high quality encodings, ii) no
> disruption of IFax products under deployment, and iii) a single integrated
> specification.
>         Disadvantages: i) Licensing issues to be resolved, and ii)
> unpredictable approval schedule due to license resolution. 
> 
>      2. Interoperable TIFF-FX: - use the new interoperability document to
> generate a TIFF-FX subset that is image/tiff interoperable, retaining the
> current image/tiff MIME type. 
>         Advantages: i) No licensing issues, and ii) predictable approval
> schedule.
>         Disadvantages: i) Loss of color and high quality encodings, ii)
> disruption of IFax products under deployment.
> 
>      3. Interoperable and non-Interoperable TIFF-FX: - use the new
> interoperability document to generate two subsets, a) Interoperable TIFF-FX,
> as per #2, and b) non-Interoperable TIFF-FX, which is composed of the
> remaining encoding subset. As with Full TIFF-FX, define both a new MIME type
> and a new file extension for the non-Interoperable TIFF-FX.
>         Advantages: i) Base-level black-and-white has no licensing issues,
> ii) predictable base-level approval schedule iii) retention of color and
> high quality encodings, iv) minimal disruption of IFax products under
> deployment.
>         Disadvantages: i) Licensing issues to be resolved for color & high
> quality, ii) unpredictable color & high quality approval schedule, iii) two
> disjoined specifications.
> 
>      4. Interoperable and Full TIFF-FX: - this is a combination of options 1
> and 2.
>         Advantages: i) Base-level black-and-white has no licensing issues,
> ii) predictable base-level approval schedule iii) retention of color and
> high quality encodings, iv) no disruption of IFax products under deployment,
> and v) base-level specification may be phased out as viewers advance.
>         Disadvantages: i) Licensing issues to be resolved for color & high
> quality, ii) unpredictable color & high quality approval schedule.

These are just ideas. Some of them may NOT be appropriate.
Also, there may be other options.

Anyway, we must have our conclusion, considering there are RFC2301 products
on the market.

--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Mon Aug 20 07:10:27 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11033
	for <fax-archive@odin.ietf.org>; Mon, 20 Aug 2001 07:10:27 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7KAXLq08989
	for ietf-fax-bks; Mon, 20 Aug 2001 03:33:21 -0700 (PDT)
Received: from smtpa.t-kougei.ac.jp (tipnsa.t-kougei.ac.jp [202.254.103.2])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7KAXIN08985
	for <ietf-fax@imc.org>; Mon, 20 Aug 2001 03:33:19 -0700 (PDT)
Received: from vw-a.t-kougei.ac.jp (vw-a [192.168.16.216])
	by smtpa.t-kougei.ac.jp (8.11.4/3.7W) with ESMTP id f7KAVVX29636;
	Mon, 20 Aug 2001 19:31:31 +0900 (JST)
Received: from tipgw.t-kougei.ac.jp (localhost [127.0.0.1])
	by vw-a.t-kougei.ac.jp (8.11.4/3.7W) with ESMTP id f7KAXZK29813;
	Mon, 20 Aug 2001 19:33:35 +0900 (JST)
Received: from image.t-kougei.ac.jp (garamond.image.t-kougei.ac.jp [172.18.5.1])
	by tipgw.t-kougei.ac.jp (8.9.3+3.2W/3.7Wpl2-01070418) with ESMTP id TAA03243;
	Mon, 20 Aug 2001 19:33:11 +0900 (JST)
Message-ID: <3B80E7FF.CB7B7E7E@image.t-kougei.ac.jp>
Date: Mon, 20 Aug 2001 19:35:44 +0900
From: Fumitaka Ono <ono@image.t-kougei.ac.jp>
X-Mailer: Mozilla 4.7 [ja] (Win98; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: ietf-fax@imc.org
Subject: [Fwd:Re: TIFF-FX Extension Set 1:]
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Dear IETF dl members:

This is rather old information but 
my comments to TIFF-FX Extension 
has not been delivered to the dl
by some reason.
So I will resend my comments to dl again.
Regards,

Fumitaka Ono
Rapporteur, JBIG SG on ISO/IEC JTC 1/SC29/WG1
=============================================
FUMITAKA ONO
Professor, Dr.
Department of Image Information Engineering
Tokyo Institute of Polytechnics
1583 Iiyama, Atsugi, Kanagawa 243-0297, JAPAN
PHONE:+81-46-242-9619, FAX:+81-46-242-9519
E-mail:ono@image.t-kougei.ac.jp
=============================================

------- Original Message --------
Subject: RE: jbig2 error mail from ono@image.t-kougei.ac.jp
Date: Wed, 15 Aug 2001 10:37:54 -0700
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
To: "F.Ono" <ono@image.t-kougei.ac.jp>

Ono-san,
Please send your message to the list again.

Thanks and best regards,
Lloyd
----- Original Message -----
From: McIntyre, Lloyd <Lloyd.McIntyre@pahv.xerox.com>
>To: 'Ono Fumitaka - Tokyo Institute of Polytechincs'
><ono@image.t-kougei.ac.jp>
>Sent: Saturday, August 04, 2001 5:30 AM
>Subject: FW: IETF dl address and your comments
> Ono-san,
> Please send your TIFF-FX Extension comments to the IETF dl below.
> We desperately need them.
>
> Thanks and best regards,
> Lloyd
>
----- Original Message -----
From: Fumitaka Ono <ono@image.t-kougei.ac.jp>
To: <ietf-fax@imc.org>
Cc: 'IBM - Ron Arps' <arps@almaden.IBM.com>
Sent: Friday, August 03, 2001 10:27 AM
Subject: Re: TIFF-FX Extension Set 1:
draft-mcintyre-tiff-fx-extension1-02

> Dear Lloyd,
> I succeeded to subscribe ietf-fax mailing list.
>
> I just read JBIG2 related sections of the
> latest TIFF-FX Extension draft according to
> your suggestion.
> Currently I have no technical comments
> on the parts.
>
> Yet some ome minor editorial corrections are
> - page 35, E1.6, 2nd and 3rd lines, 'T88' is duplicated.
> - page 47, 7th line, 'This is' is duplicated.
> - page 56, E1.7, 5th lines from the bottom, 'such JPEG'
>    might  be 'such as JPEG'
>
> Regards,
> Fumitaka Ono
> Rapporteur, JBIG SG on ISO/IEC JTC 1/SC29/WG1


From owner-ietf-fax@mail.imc.org  Tue Aug 21 06:31:35 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03822
	for <fax-archive@odin.ietf.org>; Tue, 21 Aug 2001 06:31:35 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7L9rJa13774
	for ietf-fax-bks; Tue, 21 Aug 2001 02:53:19 -0700 (PDT)
Received: from bulls.mei.co.jp (bulls.mei.co.jp [202.224.189.25])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7L9rHN13766
	for <ietf-fax@imc.org>; Tue, 21 Aug 2001 02:53:18 -0700 (PDT)
Received: by bulls.mei.co.jp (8.11.4/3.7W) with ESMTP id f7L9qZ425425;
	Tue, 21 Aug 2001 18:52:36 +0900 (JST)
Received: by dodgers.mei.co.jp (8.9.1/3.7W) with SMTP id SAA26376;
	Tue, 21 Aug 2001 18:52:34 +0900 (JST)
Received: from [133.185.137.6] by m-bb2.mgcs.mei.co.jp
          via smtpd (for [157.8.1.150]) with SMTP; 21 Aug 2001 09:52:35 UT
Received: from mlsv1.mgcs.mei.co.jp
	by mlsv0.mgcs.mei.co.jp (8.9.3/3.7W-HUB) with ESMTP id SAA20674;
	Tue, 21 Aug 2001 18:52:35 +0900 (JST)
Received: from mlsv2.rdmg.mgcs.mei.co.jp
	by mlsv1.mgcs.mei.co.jp (8.9.3/3.7W-MGCS) with ESMTP id SAA11192;
	Tue, 21 Aug 2001 18:52:34 +0900 (JST)
Received: from d23n59.rdmg.mgcs.mei.co.jp
	by mlsv2.rdmg.mgcs.mei.co.jp (8.9.3/3.7W-RDMG) with SMTP id SAA13640;
	Tue, 21 Aug 2001 18:52:34 +0900 (JST)
Message-Id: <200108210954.AA00066@d23n59.rdmg.mgcs.mei.co.jp>
From: "Toyoda, Kiyoshi" <ktoyoda@rdmg.mgcs.mei.co.jp>
Date: Tue, 21 Aug 2001 18:54:56 +0900
To: tamura@toda.ricoh.co.jp
Cc: ietf-fax@imc.org, sfoshee@Adobe.COM, Lloyd.McIntyre@pahv.xerox.com
Subject: Re: Fwd: IFX> FW: notes from the ietf FAX wg meeting at IETF 51
In-Reply-To: <20010820074741P.tamura@toda.ricoh.co.jp>
References: <20010820074741P.tamura@toda.ricoh.co.jp>
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.12
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


Tamura-san,

I comment below.

Hiroshi Tamura wrote:
>
>Some slides at the meeting:
>-------------------------------------------------------------------------------
>
>- TIFF extension beyond basic black-and-white induces incompatibility
>  with existing base tiff applications
>    Should we retreat to only base set black-and-white, retaining full
>    compatibility with existing tiff base or continue to embrace the defined
>    path that introduces new encodings for both black-and-white and color that
>    are consistent with ITU-T fax encodings?
>
>    1 If decision is to retain extended encodings then compatibility must be
>      addressed, two options are:
>        Different MIME type and file extension
>	or
>	Different MIME type and file extension  together with a new Adobe
>        issued TIFF version that encompass the TIFF-FX encodings
>
>    2 If decision is to retreat to only base black-and-white then we must:
>        Delete all TIFF-FX profiles other than S and F with constraints as follows:
>        encodings MH, MR and MMR resolutions of 200x100 and 200x200 paper size A4/letter
>
>-------------------------------------------------------------------------------
>
>These are just descriptions. Some of the above may not be appropriate.
>
>I said:
>> Anyway, I would like to confirm our conclusion at the meeting.
>> 
>> 1. Safe subset for Draft Standard Consideration
>> 2. Final agreement will be made in this ML.
>
>But, we do not decide precisely what is safe subset.

I think that we need clarify what is a safe subset. 
Is the below correct?

- all TIFF-FX profiles other than S and F with constraints as follows:
- encodings MH, MR and MMR resolutions of 200x100 and 200x200 paper size A4/letter

I would like the safe subset to cover more wide range if possible
because many manufacture already have implement Internet Fax
according to RFC2301.


>
>Lloyd said:
>> p  - One of the four options below should be selected for the
>> specification(s) that will move forward through the standards tack process:
>>      1. Full TIFF-FX: - retain the currently defined TIFF-FX draft without
>> modification of the encoding set and define both a new MIME type (e.g.
>> image/tifffx or image/tifx) and a new file extension (e.g. .tifx or .tfx).
>> The new MIME type and extension circumvents interoperability issues with
>> TIFF 6.0. 
>>         Advantages: i) Retention of color and high quality encodings, ii) no
>> disruption of IFax products under deployment, and iii) a single integrated
>> specification.
>>         Disadvantages: i) Licensing issues to be resolved, and ii)
>> unpredictable approval schedule due to license resolution. 
>> 
>>      2. Interoperable TIFF-FX: - use the new interoperability document to
>> generate a TIFF-FX subset that is image/tiff interoperable, retaining the
>> current image/tiff MIME type. 
>>         Advantages: i) No licensing issues, and ii) predictable approval
>> schedule.
>>         Disadvantages: i) Loss of color and high quality encodings, ii)
>> disruption of IFax products under deployment.
>> 
>>      3. Interoperable and non-Interoperable TIFF-FX: - use the new
>> interoperability document to generate two subsets, a) Interoperable TIFF-FX,
>> as per #2, and b) non-Interoperable TIFF-FX, which is composed of the
>> remaining encoding subset. As with Full TIFF-FX, define both a new MIME type
>> and a new file extension for the non-Interoperable TIFF-FX.
>>         Advantages: i) Base-level black-and-white has no licensing issues,
>> ii) predictable base-level approval schedule iii) retention of color and
>> high quality encodings, iv) minimal disruption of IFax products under
>> deployment.
>>         Disadvantages: i) Licensing issues to be resolved for color & high
>> quality, ii) unpredictable color & high quality approval schedule, iii) two
>> disjoined specifications.
>> 
>>      4. Interoperable and Full TIFF-FX: - this is a combination of options 1
>> and 2.
>>         Advantages: i) Base-level black-and-white has no licensing issues,
>> ii) predictable base-level approval schedule iii) retention of color and
>> high quality encodings, iv) no disruption of IFax products under deployment,
>> and v) base-level specification may be phased out as viewers advance.
>>         Disadvantages: i) Licensing issues to be resolved for color & high
>> quality, ii) unpredictable color & high quality approval schedule.
>
>These are just ideas. Some of them may NOT be appropriate.
>Also, there may be other options.
>
>Anyway, we must have our conclusion, considering there are RFC2301 products
>on the market.
>

I prefer No. 4.  It seems less disadvantage to us. It is also suggested
by Dave-san in the meeting. 

Regards,

Kiyoshi Toyoda


From owner-ietf-fax@mail.imc.org  Tue Aug 21 20:25:20 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03678
	for <fax-archive@odin.ietf.org>; Tue, 21 Aug 2001 20:25:19 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7LNS4T18694
	for ietf-fax-bks; Tue, 21 Aug 2001 16:28:04 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7LNS2N18690
	for <ietf-fax@imc.org>; Tue, 21 Aug 2001 16:28:02 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id IAA27984;
	Wed, 22 Aug 2001 08:28:02 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id ABD30030;
	Wed, 22 Aug 2001 08:28:00 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id IAA00352; Wed, 22 Aug 2001 08:27:57 +0900
To: ktoyoda@rdmg.mgcs.mei.co.jp
Cc: ietf-fax@imc.org
Subject: TIFF-FX Safe subset
In-Reply-To: <200108210954.AA00066@d23n59.rdmg.mgcs.mei.co.jp>
References: <20010820074741P.tamura@toda.ricoh.co.jp>
	<200108210954.AA00066@d23n59.rdmg.mgcs.mei.co.jp>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010822083146V.tamura@toda.ricoh.co.jp>
Date: Wed, 22 Aug 2001 08:31:46 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 39
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Thanks for your comment.

(I change the subject)

> >> Anyway, I would like to confirm our conclusion at the meeting.
> >> 
> >> 1. Safe subset for Draft Standard Consideration
> >> 2. Final agreement will be made in this ML.
> >
> >But, we do not decide precisely what is safe subset.
> 
> I think that we need clarify what is a safe subset. 
> Is the below correct?
> 
> - all TIFF-FX profiles other than S and F with constraints as follows:
> - encodings MH, MR and MMR resolutions of 200x100 and 200x200 paper size A4/letter

Unfortunately, I am not the right person to answer it.
As my personal opinion, considering the implementation report and
the license issue, we should decide it.

We may need the comment from the editors.

> I would like the safe subset to cover more wide range if possible
> because many manufacture already have implement Internet Fax
> according to RFC2301.

Right. We already have products int the market. I believe most implementers
have at least Profile F.
Now, I am collecting the implementation information of Japanese IFAX products.
I think one of our issues is color. I know Xerox has all profiles.

Is there anyone that support Color profile?

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Tue Aug 21 21:29:56 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04350
	for <fax-archive@odin.ietf.org>; Tue, 21 Aug 2001 21:29:56 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7M0ikf19910
	for ietf-fax-bks; Tue, 21 Aug 2001 17:44:46 -0700 (PDT)
Received: from AvantiServer.avantiholdings.com (durham-23-122.biz.dsl.gtei.net [4.3.23.122])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7M0iiN19906
	for <ietf-fax@imc.org>; Tue, 21 Aug 2001 17:44:44 -0700 (PDT)
Received: from JP2000 ([12.98.203.162]) by AvantiServer.avantiholdings.com with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 21 Aug 2001 17:35:48 -0700
Reply-To: <jpulera@minolta-mil.com>
From: "John Pulera" <jpulera@minolta-mil.com>
To: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>,
        "'IETF - fax WG dl'" <ietf-fax@imc.org>,
        "'IETF - John Klensin \(IAB Chair\)'" <klensin@jck.com>
Cc: "'PWG - IPPFax DL'" <ifx@pwg.org>
Subject: RE: notes from the ietf FAX wg meeting at IETF 51
Date: Tue, 21 Aug 2001 17:46:51 -0700
Message-ID: <BKEOJKEPLGGCMFCMILPIOEHICCAA.jpulera@minolta-mil.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <51B8ABCE456FD111899900805F6FD6EE067A352A@mercury.ADOC.xerox.com>
Importance: Normal
X-OriginalArrivalTime: 22 Aug 2001 00:35:48.0998 (UTC) FILETIME=[63C49260:01C12AA2]
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 8bit


I am a developer working for Minolta.

I have read about proposals to split the TIFF-FX into two documents, one
with TIFF 6.0 compatible profiles (S and F) that would be published soon and
one with the other profiles that would await resolution of IP issues.

I believe it would be better and faster to resolve the IP issues quickly and
publish TIFF-FX as a single revised document.   The revised document should
restrict the use of the existing image/tiff MIME type and .tif (or .tiff)
file name extensions to profiles S and F, and assign a new MIME type and
file name extension for the profiles J, C, L, and M (perhaps image/tifx and
.tfx (or .tifx)). By restricting image/tiff to profiles S and F, TIFF-FX
keeps compatibility with TIFF-6. By allowing image/tiff and .tif (or .tiff)
for the S and F profiles, TIFF-FX reflects what exists in many deployed
TIFF-FX devices.

Let’s call this solution option 5. It’s a variant of options 1 and 4.

If the document is split, the publishing of the document containing profiles
that are of interest to Minolta may be delayed a very long time. Also, it
will take several months to split the document and gain approval of the one
with the S and F Profiles.

If the document remains as one, we avoid spending the time to edit and gain
acceptance of the new documents. In addition, with a single document there
are more people to pressure Adobe and Xerox to agree quickly on the IP
issues.

Regards,

John Pulera
-----------------------------------------
John Pulera
Software Engineer
Minolta Systems Laboratory
jpulera@minolta-mil.com <mailto:jpulera@minolta-mil.com>


-----Original Message-----
From: owner-ietf-fax@mail.imc.org [mailto:owner-ietf-fax@mail.imc.org]On
Behalf Of McIntyre, Lloyd
Sent: Tuesday, August 14, 2001 4:15 PM
To: 'IETF - fax WG dl'; 'IETF - John Klensin (IAB Chair)'
Cc: 'PWG - IPPFax DL'
Subject: FW: notes from the ietf FAX wg meeting at IETF 51
Importance: High


Claudio and Tamura-san
My thanks to you and Graham for the excellent job in capturing the meeting
proceedings and result.
Please allow me to suggest a few clarifications below.

Regards,
Lloyd

> -----Original Message-----
> From: Claudio Allocchio [mailto:Claudio.Allocchio@garr.it]
> Sent: Thursday, August 09, 2001 9:26 AM
> To: ietf-fax@imc.org
> Cc: klensin@jck.com
> Subject: notes from the ietf FAX wg meeting at IETF 51
>
>
>
---snip---
>
>  2.2 TIFF-FX
>       draft-ietf-fax-tiff-fx-09.txt
>       draft-ietf-fax-tiff-regbis-02.txt
>
---snip---
> The question now is: can we meet all these constrains? Is TIFF the right
> choice to accomplish them?
The second sentence was not an issued raised by the IAB chair, in fact one
individual raised this issue. Please consider deleting the second sentence
or revising to read as follows:
"The question now is: can we meet all these constrains? One individual asked
whether TIFF was the right choice to accomplish them?"

> Basic TIFF does not support colors, and different resolutions, but is it
> compliant with the existing TIFF readers, and e-mail User Agents (MUAs).
Reverse the order of "is it" to read "it is".

> However, if we want to cover also the "extensions" that ITU-T is
> requesting for fax service (e.g. colors, resolutions, etc...) Basic TIFF
> is not enough, and it will need extensions.
Given that accommodation of ITU-T color and higher quality encodings was a
component of the WG charter, this sentence may be reworded to convey less of
an impression that it was an afterthought. Please consider the following
revision:
"Basic TIFF was not enough to accommodate color and higher quality ITU-T
encodings, consequently extensions were needed."

>                                                These extensions were
> specified into TIFF-FX, and ITU-T decided to adopt and reference it.
For completeness, please append "for their Internet Fax standard" to this
sentence. It should now read:
"These extensions were specified into TIFF-FX, and ITU-T decided to adopt
and reference it for their Internet Fax standard."

> However TIFF-FX is already beyond Basic TIFF.
>
> Actually there are already de facto extensions to basic TIFF
> specifications which are publicly available, and widely
> deployed within
> both TIFF readers and MUAs. All there de facto extensions are
> currently
> used in MIME type "image/tiff" and there are not interoperability
> problems.
The statement of no interoperability problems with all the de facto
extensions is inaccurate, since some deployed viewers will not read all the
extensions. Please reword the second sentence similar to the following:
"All the de facto extensions are currently used in MIME type "image/tiff"
and some have no interoperability problems."

>          However the extensions intriduced into TIFF-FX are a superset,
> and thus only some Ifax devices can correctly handle them.
A correction and softening is warranted, given that it is not only Ifax
devices that are capable of reading TIFF-FX files and the limited
readability is not an unusual issue with new extensions in general. Consider
the following:
"The extensions introduced into TIFF-FX are a superset, which are viewable
by a limited set of Ifax devices and software applications."

It is important to convey the fact that the WG took deliberate steps to
avoid incompatibility resulting from addition of new encodings by redefining
the image/tiff MIME type (i.e. RFC2302) to include an application parameter.
The results were not quite satisfactory, however, the issue was addressed
and steps were taken. Accordingly, please consider insertion of the
following paragraph:

"To avoid interoperability issues arising from introduction of the extended
color and high quality super set, the image/tiff MIME type was revised to
add application parameters. The image/tiff application parameters serve to
alert viewers to the presence of the TIFF-FX superset. Recent disclosures,
however, indicate that many readers do not pay attention to MIME application
parameters. It is the inconsistent usage of application parameters that is
at the heart of TIFF-FX incompatibility with image/tiff viewers."

>
> So, the IESG and IAB would like the WG to review and
> document, as a condition
> for advancing the TIFF specification to Draft Standard:
>
>  - Whether the choice of "interoperation with e-mail" versus
> "interoperation
>    with fax" is the right one
>  - whether a mostly-fax-only TIFF variation is the right choice
>  - Whether this should be image/tiff or image/tifffx (or equivalent)
Clarify as follows:
 "- Whether the MIME sub-type should be image/tiff or image/tifffx (or
equivalent)"

>  - hether the interoperability profile is right given these issues
Please clarify, I do not understand what is being said?

>  - and any other similar tradeoffs that might have been made
> without full
>    evaluation.

---snip---
The paragraph below appears to be lacking context of what the IPR issue is,
please prefix it with the following:
"In December 2000 Adobe provided notification of its believe that the
TIFF-FX specification exceeds the scope of its 1997 IETF license grant for
TIFF-FX development <http://www.ietf.org/ietf/IPR/Adobe-TIFF>. Inclusion of
the extended encodings within TIFF-FX was identified as reason for the claim
of exceeded scope. The validity of this claim has been questioned, given
that the grant contains no constraint on extensions within TIFF-FX. The fact
that Abode co-authored both the TIFF-FX and the revised MIME image/tiff
specifications makes it more difficult to understand the claim.
Additionally, it may be said that the claim is somewhat late, given that
TIFF-FX was issued as Proposed Standard in December 1998."

> Adobe:  the solution appears to be to have Adobe include the
> new TIFF-FX
> encodings in TIFF-7, but Adobe has not committed to produce
> TIFF-7 and It
> is not clear what produces that commitment. Moreover, even if they do
> TIFF-7, they will not commit to including the TIFF-FX
> features until at
> least Xerox releases rights to the encoding techniques for all uses of
> TIFF, not just fax and Xerox (or maybe IETF) apply formally
> to Adobe to
> have the features and tags included. At last, but not the
> least, no one at
> this IETF can commit Adobe.
In light of the attached license statement, which clearly states that Xerox
grants MRC license use within TIFF-FX and without any application space
restrictions, please correct the 2nd sentence by inserting "MRC" between
"the encoding" and changing "not just fax and Xerox (or maybe IETF) apply"
to "not just TIFF-FX, and apply". The sentence should now read:
"Moreover, even if they do TIFF-7, they will not commit to including the
TIFF-FX features until at least Xerox releases rights to the MRC encoding
techniques for all uses of TIFF, not just TIFF-FX, and apply formally to
Adobe to have the features and tags included."

>
> Xerox: Xerox is willing to release rights for all uses in
> TIFF if Adobe
> will adopt them and include them in TIFF-7. But no one here can commit
> Xerox either.
>
> Thus it seems a viable solution currently in a deadlock waiting for
> somebody to make the first move.
>
---snip---
>
> The discussion of the problem and the WG conclusions.
> -------------------------------------------------
>
Consider constraining this section to only WG conclusions and procedures to
be followed, removing the detailed he said/she said commentary. This
translates to deleting all items prior to the paragraph that starts "Claudio
A. summarised the conclusions to be reported into the minues,".
The revised title might read as follows:
"WG meeting conclusions and procedures to be followed"
 ----------------------------------------------------

This would be followed by a restructured, consolidated and clarified body as
below.

A summary of the meeting's rough consensus, along with the procedures to be
followed, is provided below with "rc" identifying rough consensus items and
"p" identifying procedure items:
rc - Interoperability with email was considered the most important choice
between email or fax interoperability.

p  - Level of interoperability should be established by conducting a test of
RFC2301 (more appropriately draft-ietf-fax-tiff-fx-09.txt) using existing
mail user agents (MUAs) and tiff capable software applications such as
PhotoShop and other tiff viewers. The software viewer test may be
accommodated by saving the RFC2301 image/tiff stream to a file with .tif or
other appropriate tiff extension.

p  - An interoperability report should be generated and used to document the
set of interoperable TIFF-FX encoding parameters, such as coder, resolution,
paper size and color components.

p  - One of the four options below should be selected for the
specification(s) that will move forward through the standards tack process:
     1. Full TIFF-FX: - retain the currently defined TIFF-FX draft without
modification of the encoding set and define both a new MIME type (e.g.
image/tifffx or image/tifx) and a new file extension (e.g. .tifx or .tfx).
The new MIME type and extension circumvents interoperability issues with
TIFF 6.0.
        Advantages: i) Retention of color and high quality encodings, ii) no
disruption of IFax products under deployment, and iii) a single integrated
specification.
        Disadvantages: i) Licensing issues to be resolved, and ii)
unpredictable approval schedule due to license resolution.

     2. Interoperable TIFF-FX: - use the new interoperability document to
generate a TIFF-FX subset that is image/tiff interoperable, retaining the
current image/tiff MIME type.
        Advantages: i) No licensing issues, and ii) predictable approval
schedule.
        Disadvantages: i) Loss of color and high quality encodings, ii)
disruption of IFax products under deployment.

     3. Interoperable and non-Interoperable TIFF-FX: - use the new
interoperability document to generate two subsets, a) Interoperable TIFF-FX,
as per #2, and b) non-Interoperable TIFF-FX, which is composed of the
remaining encoding subset. As with Full TIFF-FX, define both a new MIME type
and a new file extension for the non-Interoperable TIFF-FX.
        Advantages: i) Base-level black-and-white has no licensing issues,
ii) predictable base-level approval schedule iii) retention of color and
high quality encodings, iv) minimal disruption of IFax products under
deployment.
        Disadvantages: i) Licensing issues to be resolved for color & high
quality, ii) unpredictable color & high quality approval schedule, iii) two
disjoined specifications.

     4. Interoperable and Full TIFF-FX: - this is a combination of options 1
and 2.
        Advantages: i) Base-level black-and-white has no licensing issues,
ii) predictable base-level approval schedule iii) retention of color and
high quality encodings, iv) no disruption of IFax products under deployment,
and v) base-level specification may be phased out as viewers advance.
        Disadvantages: i) Licensing issues to be resolved for color & high
quality, ii) unpredictable color & high quality approval schedule.

rc - Option 2, Interoperable TIFF-FX, was selected to move forward at this
time.

p  - Justification of the selection must be documented and communicated to
the ITU.

p  - Both the resulting specification and the Implementors Guide should
contain explanation of the interoperability issues and countermeasures.

p  - The resulting specification(s) may be resubmitted to the IESG for Draft
Standard consideration if there are draft-ietf-fax-tiff-fx-09.txt
function/feature deletions or no changes. This means that Full TIFF-FX, with
no changes, and both the Interoperable TIFF-FX and non-Interoperable TIFF-FX
subsets, without any additions, may be resubmitted to the IESG for Draft
Standard consideration. Any required specification additions shall result in
recycle as Proposed Standard.

p  - Resolution of IPR issues associated with Full TIFF-FX and
non-Interoperable TIFF-FX needs to progress in parallel with the above
activates and the ITU should be kept informed.

---snip---

> 5.5 TIFF-FX extension issue
>      draft-ietf-fax-tiff-fx-Extension-1-02.txt
>      (drtyre-tiff-fx-extension1-02.txt)
>     darft-mcintyre-feature-schema-extension1-00.txt

> After remembering that all the issues in these documents are related to
> the previous discussion about TIFF and TIFF-FX issue, and that IPR
>problems should be clearly investigated also for these proposed
> extensions, the presentation (see slies) described the further JBIG2
> extensions.

> Larry M. asked how many in the room read the draft:  One person. As such
> the question was raised if we should continue the work, if there is
> interest in doing it or not, provided that at a certain point the
> specification will have to undego interoperability tests, and the lack of
> interest could lead to a lack of implementations.  There was at the moment
> no conclusion to ths question, as we need to check first the status of the
> TIFF issue evolution.
The second paragraph should be depersonalized and clarified to note that
there was confusion as to which specification was being addressed by the
question of number of reviewers. The question was asked toward the end of
the Schema, not the TIFF-FX Extension presentation. The respondent was a
reviewer of the Schema extension, which is a very new draft with little time
for review. Revise as follows:
"Toward the end of the Schema extension presentation a member ask how many
had read the draft, there was no clarifications as which draft was being
referenced. There was acknowledgement from on member who had reviewed the
Schema drat. The requestor then asked whether the work should be continued,
without much response. No conclusions could be drawn."




From owner-ietf-fax@mail.imc.org  Wed Aug 22 02:33:19 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26352
	for <fax-archive@odin.ietf.org>; Wed, 22 Aug 2001 02:33:19 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7M5aXq27024
	for ietf-fax-bks; Tue, 21 Aug 2001 22:36:33 -0700 (PDT)
Received: from mx.toshibatec.co.jp (mx.toshibatec.co.jp [202.215.2.15])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7M5aVN27018
	for <ietf-fax@imc.org>; Tue, 21 Aug 2001 22:36:32 -0700 (PDT)
Received: from cn.toshibatec.co.jp by mx.toshibatec.co.jp (8.8.8+Sun/3.6W TEC mailserver) id OAA07585; Wed, 22 Aug 2001 14:33:04 +0900 (JST)
Received: from president.rdl.toshibatec.co.jp by cn.toshibatec.co.jp (SMI-8.6/3.5W TEC master mailserver [99/10/07 13:34]) id OAA03137; Wed, 22 Aug 2001 14:27:39 +0900
Received: from t21012412 
Message-ID: <005601c12acb$d1b96380$8fcc459d@t21012412>
Reply-To: "Ryuji Iwazaki" <iwa@rdl.toshibatec.co.jp>
From: "Ryuji Iwazaki" <iwa@rdl.toshibatec.co.jp>
To: <ktoyoda@rdmg.mgcs.mei.co.jp>, "Hiroshi Tamura" <tamura@toda.ricoh.co.jp>
Cc: <ietf-fax@imc.org>
References: <20010820074741P.tamura@toda.ricoh.co.jp><200108210954.AA00066@d23n59.rdmg.mgcs.mei.co.jp> <20010822083146V.tamura@toda.ricoh.co.jp>
Subject: Re: TIFF-FX Safe subset
Date: Wed, 22 Aug 2001 14:32:22 +0900
Organization: TOSHIBA TEC CORPORATION
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


TOSHIBA TEC has products which implement profileS, F and J.
If a new MIME type (eg. image/tifffx) is defined for TIFF-FX,
there is an interoperability issue between existing products and new
products which
deploy the new MIME type.
It is very difficult to update the firmware of existing products in order to
handle the new MIME type, because users can not update the firmware,
service people of dealers or manufacturers have to update in users' site.

We can distinguish between TIFF V6 and TIFF-FX using RFC2302.
IFAX products use the sub-type as follows.

Content-type: image/tiff; application=faxbw

That's my idea.

Regards,

Ryuji Iwazaki
TOSHIBA TEC Corporation




From owner-ietf-fax@mail.imc.org  Wed Aug 22 07:45:50 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00693
	for <fax-archive@odin.ietf.org>; Wed, 22 Aug 2001 07:45:49 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7MAgor01564
	for ietf-fax-bks; Wed, 22 Aug 2001 03:42:50 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7MAglN01560
	for <ietf-fax@imc.org>; Wed, 22 Aug 2001 03:42:48 -0700 (PDT)
Received: from azteca.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.74])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id TAA18320;
	Wed, 22 Aug 2001 19:35:58 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by azteca.isd.ricoh.co.jp (Mirapoint)
	with SMTP id AAY60497;
	Wed, 22 Aug 2001 19:35:58 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id TAA05726; Wed, 22 Aug 2001 19:35:51 +0900
To: jpulera@minolta-mil.com
Cc: Lloyd.McIntyre@pahv.xerox.com, ietf-fax@imc.org, klensin@jck.com,
        ifx@pwg.org
Subject: RE: notes from the ietf FAX wg meeting at IETF 51
In-Reply-To: <BKEOJKEPLGGCMFCMILPIOEHICCAA.jpulera@minolta-mil.com>
References: <51B8ABCE456FD111899900805F6FD6EE067A352A@mercury.ADOC.xerox.com>
	<BKEOJKEPLGGCMFCMILPIOEHICCAA.jpulera@minolta-mil.com>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010822193942U.tamura@toda.ricoh.co.jp>
Date: Wed, 22 Aug 2001 19:39:42 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 33
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


John,

> I believe it would be better and faster to resolve the IP issues quickly and
> publish TIFF-FX as a single revised document.   The revised document should
> restrict the use of the existing image/tiff MIME type and .tif (or .tiff)
> file name extensions to profiles S and F, and assign a new MIME type and
> file name extension for the profiles J, C, L, and M (perhaps image/tifx and
> .tfx (or .tifx)). By restricting image/tiff to profiles S and F, TIFF-FX
> keeps compatibility with TIFF-6. By allowing image/tiff and .tif (or .tiff)
> for the S and F profiles, TIFF-FX reflects what exists in many deployed
> TIFF-FX devices.
> 
> Let’s call this solution option 5. It’s a variant of options 1 and 4.

Yes, a good idea. One document is better for all implementers, I think.
But, how do we separate is the discussion issue.

<snip>

> If the document remains as one, we avoid spending the time to edit and gain
> acceptance of the new documents. In addition, with a single document there
> are more people to pressure Adobe and Xerox to agree quickly on the IP
> issues.

Right. We need to avoid spending time for our market.
Thanks for your comment.

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp




From owner-ietf-fax@mail.imc.org  Wed Aug 22 07:45:56 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00724
	for <fax-archive@odin.ietf.org>; Wed, 22 Aug 2001 07:45:56 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.3/8.11.3) id f7MAmBu01672
	for ietf-fax-bks; Wed, 22 Aug 2001 03:48:11 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.3/8.11.3) with ESMTP id f7MAm9N01666
	for <ietf-fax@imc.org>; Wed, 22 Aug 2001 03:48:09 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id TAA21600;
	Wed, 22 Aug 2001 19:48:05 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id ABD47736;
	Wed, 22 Aug 2001 19:47:58 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id TAA05832; Wed, 22 Aug 2001 19:47:52 +0900
To: iwa@rdl.toshibatec.co.jp
Cc: ktoyoda@rdmg.mgcs.mei.co.jp, ietf-fax@imc.org
Subject: Re: TIFF-FX Safe subset
In-Reply-To: <005601c12acb$d1b96380$8fcc459d@t21012412>
References: <200108210954.AA00066@d23n59.rdmg.mgcs.mei.co.jp>
	<20010822083146V.tamura@toda.ricoh.co.jp>
	<005601c12acb$d1b96380$8fcc459d@t21012412>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010822195145W.tamura@toda.ricoh.co.jp>
Date: Wed, 22 Aug 2001 19:51:45 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 37
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Iwazaki-san,

> TOSHIBA TEC has products which implement profileS, F and J.
> If a new MIME type (eg. image/tifffx) is defined for TIFF-FX,
> there is an interoperability issue between existing products and new
> products which
> deploy the new MIME type.
> It is very difficult to update the firmware of existing products in order to
> handle the new MIME type, because users can not update the firmware,
> service people of dealers or manufacturers have to update in users' site.
> 
> We can distinguish between TIFF V6 and TIFF-FX using RFC2302.
> IFAX products use the sub-type as follows.
> 
> Content-type: image/tiff; application=faxbw
> 
> That's my idea.

After the meeting, I talked and mailed more with lots of people.
I understand the situation.

Yes. You are right. RFC2302 intension is what you are suggesting.
But, unfortunately, it seems that the application parameter is not
handled by most viewers or something. This is one of the reason for
compatibility issue.

Even if Profile J will not be included in the safe subset,
it is better to address that some previous machines use image/tiff
for all Profiles in the new document. 

Any other implementation information is welcome.

Regards
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp



From subs-reminder@imc.org  Thu Aug 23 21:40:09 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05983
	for <fax-archive@odin.ietf.org>; Thu, 23 Aug 2001 21:40:08 -0400 (EDT)
From: subs-reminder@imc.org
Received: by above.proper.com (8.11.6/8.11.3) id f7O1fNs28375;
	Thu, 23 Aug 2001 18:41:23 -0700 (PDT)
Date: Thu, 23 Aug 2001 18:41:23 -0700 (PDT)
Message-Id: <200108240141.f7O1fNs28375@above.proper.com>
To: fax-archive@ietf.org
Subject: [[362960454]] Subscription to ietf-fax for fax-archive@lists.ietf.org

Greetings. This message is a periodic reminder that
     fax-archive@lists.ietf.org
is subscribed to the
     ietf-fax
mailing list.

There are two purposes for this message:
- If this message is bounced by your mail server, I can remove you from
  the mailing list and reduce waste of bandwidth and resources. (If you
  are reading this message, it clearly didn't get bounced!)
- Some people stay subscribed to mailing lists even though they do not
  want to because they do not know how to unsubscribe. 

If you want to stay subscribed to the ietf-fax mailing list,
you do not need to do anything.

On the other hand, if you want to unsubscribe from this list, go to the
following link:
     <http://www.imc.org/Unsubs/362960454>
You can also unsubscribe by email. To do so, you can respond to this
message and I will unsubscribe you by hand in the next few days.
Alternatively, you can send a plain-text message to:
     ietf-fax-request@imc.org
with the single word
     unsubscribe
in the body of the message.

If you have any questions, feel free to contact me.

--Paul Hoffman, list administrator


From owner-ietf-fax@mail.imc.org  Fri Aug 24 15:10:58 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12818
	for <fax-archive@odin.ietf.org>; Fri, 24 Aug 2001 15:10:57 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7OIEjl28401
	for ietf-fax-bks; Fri, 24 Aug 2001 11:14:45 -0700 (PDT)
Received: from postoffice.netsilicon.com (postoffice.netsilicon.com [199.93.124.180])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7OIEhD28396
	for <ietf-fax@imc.org>; Fri, 24 Aug 2001 11:14:43 -0700 (PDT)
Received: by postoffice.netsilicon.com with Internet Mail Service (5.5.2650.21)
	id <RL06NJJK>; Fri, 24 Aug 2001 14:13:53 -0400
Message-ID: <7535D222E514D511AC5A00A0C9D346D00ADF8A@postoffice.netsilicon.com>
From: "Wagner,William" <wwagner@netsilicon.com>
To: "'ietf-fax@imc.org'" <ietf-fax@imc.org>
Subject: RE: notes from the ietf FAX wg meeting at IETF 51
Date: Fri, 24 Aug 2001 14:13:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>




Tamura-san,

I think the main point that John makes, that there should be just one
document defining TIFF-FX, is the critical point. The advantage of quickly
generating a  document defining "safe" TIFF-FX is specious since many
companies, including the companies with which NetSilicon works, already are
shipping equipment which includes advanced TIFF-FX. The consensus on what is
"safe" will be colored by the fact that no one wants to agree to a
definition that makes their existing equipment nonstandard. By fully
defining all existing and planned TIFF-FX variations as John suggests, a
clear statement is made about what variations exist and how each is to be
identified.  Fragmenting this information  in multiple documents will lead
to confusion, which is contrary to the purpose of a standard. We also
believe that a single document will, in the last analysis, provide for a
faster consensus on the more feature rich modes which are necessary to make
IFAX viable.

William A. Wagner (Bill Wagner)
Director of Technology
Imaging Division
NetSilicon, Inc.
781-398-4588


-----Original Message-----
From: Hiroshi Tamura [mailto:tamura@toda.ricoh.co.jp]
Sent: Wednesday, August 22, 2001 6:40 AM
To: jpulera@minolta-mil.com
Cc: Lloyd.McIntyre@pahv.xerox.com; ietf-fax@imc.org; klensin@jck.com;
ifx@pwg.org
Subject: RE: notes from the ietf FAX wg meeting at IETF 51



John,

> I believe it would be better and faster to resolve the IP issues quickly
and
> publish TIFF-FX as a single revised document.   The revised document
should
> restrict the use of the existing image/tiff MIME type and .tif (or .tiff)
> file name extensions to profiles S and F, and assign a new MIME type and
> file name extension for the profiles J, C, L, and M (perhaps image/tifx
and
> .tfx (or .tifx)). By restricting image/tiff to profiles S and F, TIFF-FX
> keeps compatibility with TIFF-6. By allowing image/tiff and .tif (or
.tiff)
> for the S and F profiles, TIFF-FX reflects what exists in many deployed
> TIFF-FX devices.
> 
> Let's call this solution option 5. It's a variant of options 1 and 4.

Yes, a good idea. One document is better for all implementers, I think.
But, how do we separate is the discussion issue.

<snip>

> If the document remains as one, we avoid spending the time to edit and
gain
> acceptance of the new documents. In addition, with a single document there
> are more people to pressure Adobe and Xerox to agree quickly on the IP
> issues.

Right. We need to avoid spending time for our market.
Thanks for your comment.

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Fri Aug 24 17:10:08 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15598
	for <fax-archive@odin.ietf.org>; Fri, 24 Aug 2001 17:10:08 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7OKPOh06513
	for ietf-fax-bks; Fri, 24 Aug 2001 13:25:24 -0700 (PDT)
Received: from cissc.cisoc.canon.com (keymaster.cis.canon.com [63.88.207.66])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7OKPMD06509
	for <ietf-fax@imc.org>; Fri, 24 Aug 2001 13:25:22 -0700 (PDT)
Received: by cissc.cisoc.canon.com with Internet Mail Service (5.5.2653.19)
	id <RRXJZRGP>; Fri, 24 Aug 2001 13:24:15 -0700
Message-ID: <6C940F5153E5D211937A0090274E8D8B03E884A0@cissc.cisoc.canon.com>
From: "Farrell, Lee" <lfarrell@cissc.canon.com>
To: "'Hiroshi Tamura'" <tamura@toda.ricoh.co.jp>, jpulera@minolta-mil.com
Cc: Lloyd.McIntyre@pahv.xerox.com, ietf-fax@imc.org, klensin@jck.com,
        ifx@pwg.org
Subject: RE: IFX> RE: notes from the ietf FAX wg meeting at IETF 51
Date: Fri, 24 Aug 2001 13:24:14 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


I agree with John Pulera's "solution option 5".  One document is best.

lee
===========================
Lee Farrell
Canon Information Systems
110 Innovation Drive
Irvine, CA  92612
(949) 856-7163 - voice
(949) 856-7510 - fax
lfarrell@cissc.canon.com
===========================
 

-----Original Message-----
From: Hiroshi Tamura [mailto:tamura@toda.ricoh.co.jp]
Sent: Wednesday, August 22, 2001 3:40 AM
To: jpulera@minolta-mil.com
Cc: Lloyd.McIntyre@pahv.xerox.com; ietf-fax@imc.org; klensin@jck.com;
ifx@pwg.org
Subject: IFX> RE: notes from the ietf FAX wg meeting at IETF 51


John,

> I believe it would be better and faster to resolve the IP issues quickly
and
> publish TIFF-FX as a single revised document.   The revised document
should
> restrict the use of the existing image/tiff MIME type and .tif (or .tiff)
> file name extensions to profiles S and F, and assign a new MIME type and
> file name extension for the profiles J, C, L, and M (perhaps image/tifx
and
> .tfx (or .tifx)). By restricting image/tiff to profiles S and F, TIFF-FX
> keeps compatibility with TIFF-6. By allowing image/tiff and .tif (or
.tiff)
> for the S and F profiles, TIFF-FX reflects what exists in many deployed
> TIFF-FX devices.
> 
> Let's call this solution option 5. It's a variant of options 1 and 4.

Yes, a good idea. One document is better for all implementers, I think.
But, how do we separate is the discussion issue.

<snip>

> If the document remains as one, we avoid spending the time to edit and
gain
> acceptance of the new documents. In addition, with a single document there
> are more people to pressure Adobe and Xerox to agree quickly on the IP
> issues.

Right. We need to avoid spending time for our market.
Thanks for your comment.

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Fri Aug 24 17:23:32 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15775
	for <fax-archive@odin.ietf.org>; Fri, 24 Aug 2001 17:23:32 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7OKhiJ06840
	for ietf-fax-bks; Fri, 24 Aug 2001 13:43:44 -0700 (PDT)
Received: from e32.bld.us.ibm.com (e32.co.us.ibm.com [32.97.110.130])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7OKhhD06836
	for <ietf-fax@imc.org>; Fri, 24 Aug 2001 13:43:43 -0700 (PDT)
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.99.140.23])
	by e32.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id QAA56938;
	Fri, 24 Aug 2001 16:38:50 -0400
Received: from d03nm070.boulder.ibm.com (d03nm070.boulder.ibm.com [9.99.140.54])
	by westrelay02.boulder.ibm.com (8.11.1m3/NCO v4.97.1) with ESMTP id f7OKdiN185234;
	Fri, 24 Aug 2001 14:39:44 -0600
To: "Farrell, Lee" <lfarrell@cissc.canon.com>
Cc: ietf-fax@imc.org, ifx@pwg.org, jpulera@minolta-mil.com, klensin@jck.com,
        Lloyd.McIntyre@pahv.xerox.com, owner-ifx@pwg.org,
        "'Hiroshi Tamura'" <tamura@toda.ricoh.co.jp>
MIME-Version: 1.0
Subject: RE: IFX> RE: notes from the ietf FAX wg meeting at IETF 51
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF230A49CB.98C0C452-ON87256AB2.007166FE@boulder.ibm.com>
From: "Harry Lewis" <harryl@us.ibm.com>
Date: Fri, 24 Aug 2001 14:39:43 -0600
X-MIMETrack: Serialize by Router on D03NM070/03/M/IBM(Release 5.0.8 |June 18, 2001) at
 08/24/2001 02:39:44 PM,
	Serialize complete at 08/24/2001 02:39:44 PM
Content-Type: text/plain; charset="us-ascii"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


I also agree with the "one document" approach... IF the IP issues can be 
resolved quickly!
---------------------------------------------- 
Harry Lewis 
IBM Printing Systems 
---------------------------------------------- 




"Farrell, Lee" <lfarrell@cissc.canon.com>
Sent by: owner-ifx@pwg.org
08/24/2001 02:24 PM

 
        To:     "'Hiroshi Tamura'" <tamura@toda.ricoh.co.jp>, jpulera@minolta-mil.com
        cc:     Lloyd.McIntyre@pahv.xerox.com, ietf-fax@imc.org, klensin@jck.com, 
ifx@pwg.org
        Subject:        RE: IFX> RE: notes from the ietf FAX wg meeting at IETF 51

 

I agree with John Pulera's "solution option 5".  One document is best.

lee
===========================
Lee Farrell
Canon Information Systems
110 Innovation Drive
Irvine, CA  92612
(949) 856-7163 - voice
(949) 856-7510 - fax
lfarrell@cissc.canon.com
===========================
 

-----Original Message-----
From: Hiroshi Tamura [mailto:tamura@toda.ricoh.co.jp]
Sent: Wednesday, August 22, 2001 3:40 AM
To: jpulera@minolta-mil.com
Cc: Lloyd.McIntyre@pahv.xerox.com; ietf-fax@imc.org; klensin@jck.com;
ifx@pwg.org
Subject: IFX> RE: notes from the ietf FAX wg meeting at IETF 51


John,

> I believe it would be better and faster to resolve the IP issues quickly
and
> publish TIFF-FX as a single revised document.   The revised document
should
> restrict the use of the existing image/tiff MIME type and .tif (or 
.tiff)
> file name extensions to profiles S and F, and assign a new MIME type and
> file name extension for the profiles J, C, L, and M (perhaps image/tifx
and
> .tfx (or .tifx)). By restricting image/tiff to profiles S and F, TIFF-FX
> keeps compatibility with TIFF-6. By allowing image/tiff and .tif (or
.tiff)
> for the S and F profiles, TIFF-FX reflects what exists in many deployed
> TIFF-FX devices.
> 
> Let's call this solution option 5. It's a variant of options 1 and 4.

Yes, a good idea. One document is better for all implementers, I think.
But, how do we separate is the discussion issue.

<snip>

> If the document remains as one, we avoid spending the time to edit and
gain
> acceptance of the new documents. In addition, with a single document 
there
> are more people to pressure Adobe and Xerox to agree quickly on the IP
> issues.

Right. We need to avoid spending time for our market.
Thanks for your comment.

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp






From owner-ietf-fax@mail.imc.org  Fri Aug 24 20:26:36 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17360
	for <fax-archive@odin.ietf.org>; Fri, 24 Aug 2001 20:26:36 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7ONmA609734
	for ietf-fax-bks; Fri, 24 Aug 2001 16:48:10 -0700 (PDT)
Received: from triton.hitachi-hkis.com (mailport.hitachi-hkis.com [192.101.159.107])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7ONmAD09730
	for <ietf-fax@imc.org>; Fri, 24 Aug 2001 16:48:10 -0700 (PDT)
Received: by triton.hitachi-hkis.com with Internet Mail Service (5.5.2653.19)
	id <QPBBN75Z>; Fri, 24 Aug 2001 16:55:00 -0700
Message-ID: <3BC1BD0C7E6DD411A13200508BDCC83DA6E96F@triton.hitachi-hkis.com>
From: "Bergman, Ron" <Ron.Bergman@hitachi-hkis.com>
To: "'ietf-fax@imc.org'" <ietf-fax@imc.org>
Subject: FW: IFX> RE: notes from the ietf FAX wg meeting at IETF 51
Date: Fri, 24 Aug 2001 16:55:00 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>




-----Original Message-----
From: Bergman, Ron 
Sent: Friday, August 24, 2001 1:32 PM
To: 'Wagner,William'; 'Hiroshi Tamura'; jpulera@minolta-mil.com
Cc: ietf-fax@imc.org; ifx@pwg.org
Subject: RE: IFX> RE: notes from the ietf FAX wg meeting at IETF 51


I agree completely with John Pulera's recommendation for one document and
Bill Wagner's recent comments.  The Printer Working Group has been making
very good progress on the IPP FAX initiate and I believe that, unless there
remains a unified document, this effort will suffer serious delays.

What really surprises me on this subject is the fact that RFC 2301 was
officially published in March 1998, with public drafts available in late
1997, and this is only now a major issue.  Be that as it may, we need to now
quickly devise a plan that satisfies both Adobe and Xerox, but does not
scrape all the work on the TIFF-FX extensions.

	Ron Bergman	
	Hitachi Koki Imaging Solutions


-----Original Message-----
From: Wagner,William [mailto:wwagner@netsilicon.com]
Sent: Friday, August 24, 2001 9:14 AM
To: 'Hiroshi Tamura'; jpulera@minolta-mil.com
Cc: Lloyd.McIntyre@pahv.xerox.com; ietf-fax@imc.org; klensin@jck.com;
ifx@pwg.org
Subject: IFX> RE: notes from the ietf FAX wg meeting at IETF 51


Tamura-san,

I think the main point that John makes, that there should be just one
document defining TIFF-FX, is the critical point. The advantage of quickly
generating a  document defining "safe" TIFF-FX is specious since many
companies, including the companies with which NetSilicon works, already are
shipping equipment which includes advanced TIFF-FX. The consensus on what is
"safe" will be colored by the fact that no one wants to agree to a
definition that makes their existing equipment nonstandard. By fully
defining all existing and planned TIFF-FX variations as John suggests, a
clear statement is made about what variations exist and how each is to be
identified.  Fragmenting this information  in multiple documents will lead
to confusion, which is contrary to the purpose of a standard. We also
believe that a single document will, in the last analysis, provide for a
faster consensus on the more feature rich modes which are necessary to make
IFAX viable.

William A. Wagner (Bill Wagner)
Director of Technology
Imaging Division
NetSilicon, Inc.
781-398-4588


-----Original Message-----
From: Hiroshi Tamura [mailto:tamura@toda.ricoh.co.jp]
Sent: Wednesday, August 22, 2001 6:40 AM
To: jpulera@minolta-mil.com
Cc: Lloyd.McIntyre@pahv.xerox.com; ietf-fax@imc.org; klensin@jck.com;
ifx@pwg.org
Subject: RE: notes from the ietf FAX wg meeting at IETF 51



John,

> I believe it would be better and faster to resolve the IP issues quickly
and
> publish TIFF-FX as a single revised document.   The revised document
should
> restrict the use of the existing image/tiff MIME type and .tif (or .tiff)
> file name extensions to profiles S and F, and assign a new MIME type and
> file name extension for the profiles J, C, L, and M (perhaps image/tifx
and
> .tfx (or .tifx)). By restricting image/tiff to profiles S and F, TIFF-FX
> keeps compatibility with TIFF-6. By allowing image/tiff and .tif (or
.tiff)
> for the S and F profiles, TIFF-FX reflects what exists in many deployed
> TIFF-FX devices.
> 
> Let's call this solution option 5. It's a variant of options 1 and 4.

Yes, a good idea. One document is better for all implementers, I think.
But, how do we separate is the discussion issue.

<snip>

> If the document remains as one, we avoid spending the time to edit and
gain
> acceptance of the new documents. In addition, with a single document there
> are more people to pressure Adobe and Xerox to agree quickly on the IP
> issues.

Right. We need to avoid spending time for our market.
Thanks for your comment.

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: tamura@toda.ricoh.co.jp


From owner-ietf-fax@mail.imc.org  Mon Aug 27 18:16:43 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02533
	for <fax-archive@odin.ietf.org>; Mon, 27 Aug 2001 18:16:41 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7RLaNt27974
	for ietf-fax-bks; Mon, 27 Aug 2001 14:36:23 -0700 (PDT)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7RLaMD27970
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 14:36:22 -0700 (PDT)
Received: from co7040exch001p.wins.lucent.com (h135-39-1-40.lucent.com [135.39.1.40])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f7RLaNX15570
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 17:36:23 -0400 (EDT)
Received: by co7040exch001p.milehi.lucent.com with Internet Mail Service (5.5.2650.21)
	id <PGJ9RFXW>; Mon, 27 Aug 2001 15:36:13 -0600
Message-ID: <0096D8500C92D211BAEB0008C7F4906C04CD3990@co7040exch002u.milehi.lucent.com>
From: "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>
To: receipt@cs.utk.edu
Cc: vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Mon, 27 Aug 2001 15:36:12 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C12F40.4ACAC660"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C12F40.4ACAC660
Content-Type: text/plain;
	charset="iso-8859-1"


The following ID announcement is for a revision to the MDN specification in
preparation for Draft Standard.  Please note:  Many seemingly unimplemented
dispositions and all disposition modifiers have been removed.  If someone
can name TWO interoperable implementations of any of the deleted
dispositions or disposition modifiers, I will be happy to add them back into
the document.

Note that the requirements for draft standard are explicit that all features
and options need to have at least two, interoperable implementations.  If
they are still useful, the unimplemented dispositions deleted from this
document may be standardized at a later date as an MDN extension.  

This document also adds an additional section for gateway advice.  The
previous document was silent about what to do when gatewaying a MDN request
into a foreign network.  Given that most email networks do not have a
separate disposition-notification-to: recipient, that was a bit of an
oversight.

Please review and send comments.  It is my hope that we can quickly advance
this to Draft Standard. 

Thank you.

Greg Vaudreuil.


------_=_NextPart_000_01C12F40.4ACAC660
Content-Type: message/rfc822
Content-Description: I-D ACTION:draft-vaudreuil-mdnbis-00.txt

Message-ID: <200108271048.GAA10077@ietf.org>
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
To: 
Subject: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Mon, 27 Aug 2001 04:48:53 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_002_01C12F40.4ACAC660"


------_=_NextPart_002_01C12F40.4ACAC660
Content-Type: text/plain;
	charset="iso-8859-1"

A New Internet-Draft is available from the on-line Internet-Drafts
directories.


	Title		: Message Disposition Notification
	Author(s)	: T. Hansen, G. Vaudreuil
	Filename	: draft-vaudreuil-mdnbis-00.txt
	Pages		: 30
	Date		: 24-Aug-01
	
This memo defines a MIME content-type that may be used by a mail user 
agent (MUA) or electronic mail gateway to report the disposition of a 
message after it has been successfully delivered to a recipient.  This 
content-type is intended to be machine-processable.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-vaudreuil-mdnbis-00.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-vaudreuil-mdnbis-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-vaudreuil-mdnbis-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.


------_=_NextPart_002_01C12F40.4ACAC660
Content-Type: message/rfc822

To: 
Subject: 
Date: Mon, 27 Aug 2001 08:05:17 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_004_01C12F40.4ACAC660"


------_=_NextPart_004_01C12F40.4ACAC660
Content-Type: text/plain



------_=_NextPart_004_01C12F40.4ACAC660
Content-Type: application/octet-stream;
	name="ATT27720"
Content-Disposition: attachment;
	filename="ATT27720"

Content-type: message/external-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20010824105707.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-vaudreuil-mdnbis-00.txt

------_=_NextPart_004_01C12F40.4ACAC660
Content-Type: message/external-body;
	site="internet-drafts";
	dir="draft-vaudreuil-mdnbis-00.txt";
	mode="ftp.ietf.org";
	access-type="anon-ftp"


------_=_NextPart_004_01C12F40.4ACAC660--

------_=_NextPart_002_01C12F40.4ACAC660--

------_=_NextPart_000_01C12F40.4ACAC660--


From owner-ietf-fax@mail.imc.org  Mon Aug 27 18:53:56 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03528
	for <fax-archive@odin.ietf.org>; Mon, 27 Aug 2001 18:53:55 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7RMJxc28676
	for ietf-fax-bks; Mon, 27 Aug 2001 15:19:59 -0700 (PDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7RMJwD28672
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 15:19:58 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id f7RMHjJ28165;
	Mon, 27 Aug 2001 15:18:01 -0700 (PDT)
Received: from DWINGW2K (dwings-dsl4.cisco.com [10.19.89.165])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAI90313;
	Mon, 27 Aug 2001 15:19:36 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "Vaudreuil, Greg M \(Greg\)" <gregv@lucent.com>, <receipt@cs.utk.edu>
Cc: <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
Subject: RE: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Mon, 27 Aug 2001 15:19:36 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGEENOEHAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <0096D8500C92D211BAEB0008C7F4906C04CD3990@co7040exch002u.milehi.lucent.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Greg,

Thanks for forwarding this.

> The following ID announcement is for a revision to the MDN specification in
> preparation for Draft Standard.  Please note:  Many seemingly unimplemented
> dispositions and all disposition modifiers have been removed.

The ABNF in section 3.2.6 seems to still list the disposition modifiers.

> If someone
> can name TWO interoperable implementations of any of the deleted
> dispositions or disposition modifiers, I will be happy to add them
> back into the document.
>
> Note that the requirements for draft standard are explicit that
> all features
> and options need to have at least two, interoperable implementations.  If
> they are still useful, the unimplemented dispositions deleted from this
> document may be standardized at a later date as an MDN extension.
>
> This document also adds an additional section for gateway advice.  The
> previous document was silent about what to do when gatewaying a MDN request
> into a foreign network.  Given that most email networks do not have a
> separate disposition-notification-to: recipient, that was a bit of an
> oversight.

Section 8.3 has a sentence which begins:

  In other most email systems,

which should be corrected.

> Please review and send comments.  It is my hope that we can quickly advance
> this to Draft Standard.

Section 3.2.2 and the 'Status of this memo' section both seem to be missing
some runoff commands to format the text correctly.

-d




From owner-ietf-fax@mail.imc.org  Mon Aug 27 19:27:56 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04194
	for <fax-archive@odin.ietf.org>; Mon, 27 Aug 2001 19:27:56 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7RMrqw29365
	for ietf-fax-bks; Mon, 27 Aug 2001 15:53:52 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7RMrnD29356
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 15:53:50 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id HAA18369;
	Tue, 28 Aug 2001 07:53:34 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id ABE25041;
	Tue, 28 Aug 2001 07:53:33 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id HAA22330; Tue, 28 Aug 2001 07:53:30 +0900
To: gregv@lucent.com
Cc: receipt@cs.utk.edu, vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: Re: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
In-Reply-To: <0096D8500C92D211BAEB0008C7F4906C04CD3990@co7040exch002u.milehi.lucent.com>
References: <0096D8500C92D211BAEB0008C7F4906C04CD3990@co7040exch002u.milehi.lucent.com>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010828075728O.tamura@toda.ricoh.co.jp>
Date: Tue, 28 Aug 2001 07:57:28 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 26
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Greg,

> The following ID announcement is for a revision to the MDN specification in
> preparation for Draft Standard.  Please note:  Many seemingly unimplemented
> dispositions and all disposition modifiers have been removed.  If someone
> can name TWO interoperable implementations of any of the deleted
> dispositions or disposition modifiers, I will be happy to add them back into
> the document.
> 
> Note that the requirements for draft standard are explicit that all features
> and options need to have at least two, interoperable implementations.  If
> they are still useful, the unimplemented dispositions deleted from this
> document may be standardized at a later date as an MDN extension.  

I do not read all, but I say,

Some Ifax devices already use:
"dispatched" or "processed" without modifiers
  when succesfully decoding the received TIFF-FX file
"processed/error" in the case of the failure.

Regards,
--
Hiroshi Tamura, Ricoh Company, LTD.
E-mail: tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Mon Aug 27 20:03:01 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04664
	for <fax-archive@odin.ietf.org>; Mon, 27 Aug 2001 20:03:00 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7RNT8V00168
	for ietf-fax-bks; Mon, 27 Aug 2001 16:29:08 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7RNT7D00164
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 16:29:07 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f7RNTOH03885;
	Mon, 27 Aug 2001 16:29:24 -0700 (PDT)
Received: from DWINGW2K (dwings-dsl4.cisco.com [10.19.89.165])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAI92040;
	Mon, 27 Aug 2001 16:22:19 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "Hiroshi Tamura" <tamura@toda.ricoh.co.jp>, <gregv@lucent.com>
Cc: <receipt@cs.utk.edu>, <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
Subject: RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Mon, 27 Aug 2001 16:22:18 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGGEOFEHAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <20010828075728O.tamura@toda.ricoh.co.jp>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


> > Note that the requirements for draft standard are explicit that
> all features
> > and options need to have at least two, interoperable implementations.  If
> > they are still useful, the unimplemented dispositions deleted from this
> > document may be standardized at a later date as an MDN extension.
>
> I do not read all, but I say,
>
> Some Ifax devices already use:
> "dispatched" or "processed" without modifiers
>   when succesfully decoding the received TIFF-FX file
> "processed/error" in the case of the failure.

Those devices will remain compliant with the Proposed Standard RFC2298,
but won't be compliant with the Draft Standard that Greg is authoring.


As soon as Greg's document becomes an RFC, I'll ask our development
group here in Cisco to bring our implementation in line with his
new Draft Standard.

-d



From owner-ietf-fax@mail.imc.org  Mon Aug 27 20:27:30 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05001
	for <fax-archive@odin.ietf.org>; Mon, 27 Aug 2001 20:27:30 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7RNsJP00713
	for ietf-fax-bks; Mon, 27 Aug 2001 16:54:19 -0700 (PDT)
Received: from umbriel.eastgw.xerox.com (umbriel.xerox.com [208.140.33.26])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7RNsID00709
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 16:54:18 -0700 (PDT)
Received: from godzilla.ADOC.xerox.com (godzilla.ADOC.xerox.com [13.242.128.10])
	by umbriel.eastgw.xerox.com (8.9.3/8.9.3) with ESMTP id TAA03749;
	Mon, 27 Aug 2001 19:54:11 -0400 (EDT)
Received: from mercury.adoc.xerox.com (mercury [13.242.100.20])
	by godzilla.ADOC.xerox.com (8.8.8+Sun/8.8.8/ADOC-HUB-1.7) with ESMTP id QAA16869;
	Mon, 27 Aug 2001 16:54:17 -0700 (PDT)
Received: by mercury.ADOC.xerox.com with Internet Mail Service (5.5.2653.19)
	id <RLRRMH28>; Mon, 27 Aug 2001 16:54:17 -0700
Message-ID: <51B8ABCE456FD111899900805F6FD6EE067A3575@mercury.ADOC.xerox.com>
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
To: "'Dan Wing'" <dwing@cisco.com>, Hiroshi Tamura <tamura@toda.ricoh.co.jp>,
        gregv@lucent.com
Cc: receipt@cs.utk.edu, vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Mon, 27 Aug 2001 16:54:16 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


My understanding is that the "dispatched" feature may be retained if
information can be provided to verify that there are interoperable
implementations.
Tamura-san is it possible to have two or more manufacturers document
interoperability of sending and receiving MDN with the dispatched feature?

Lloyd

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Monday, August 27, 2001 4:22 PM
> To: Hiroshi Tamura; gregv@lucent.com
> Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> 
> 
> 
> > > Note that the requirements for draft standard are explicit that
> > all features
> > > and options need to have at least two, interoperable 
> implementations.  If
> > > they are still useful, the unimplemented dispositions 
> deleted from this
> > > document may be standardized at a later date as an MDN extension.
> >
> > I do not read all, but I say,
> >
> > Some Ifax devices already use:
> > "dispatched" or "processed" without modifiers
> >   when succesfully decoding the received TIFF-FX file
> > "processed/error" in the case of the failure.
> 
> Those devices will remain compliant with the Proposed 
> Standard RFC2298,
> but won't be compliant with the Draft Standard that Greg is authoring.
> 
> 
> As soon as Greg's document becomes an RFC, I'll ask our development
> group here in Cisco to bring our implementation in line with his
> new Draft Standard.
> 
> -d
> 


From owner-ietf-fax@mail.imc.org  Mon Aug 27 20:57:33 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05450
	for <fax-archive@odin.ietf.org>; Mon, 27 Aug 2001 20:57:33 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7S0Ntf01249
	for ietf-fax-bks; Mon, 27 Aug 2001 17:23:55 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7S0NsD01245
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 17:23:54 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f7S0Nkl14137;
	Mon, 27 Aug 2001 17:23:46 -0700 (PDT)
Received: from DWINGW2K (dwings-dsl4.cisco.com [10.19.89.165])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAI93737;
	Mon, 27 Aug 2001 17:23:45 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "Jason McCurry" <jasonm@speakeasy.org>
Cc: <vpim@lists.neystadt.org>, <ietf-fax@imc.org>,
        "Vaudreuil, Greg M \(Greg\)" <gregv@lucent.com>, <receipt@cs.utk.edu>
Subject: RE: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Mon, 27 Aug 2001 17:23:44 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGCEOJEHAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <EOEALJLHGFBHHJFKLHOBCENMCAAA.jasonm@speakeasy.org>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Jason,

We're powerless to unsubscribe you.  None
of us are in charge of these mailing lists.


In looking at the list of recipients, I am
guessing you are subscribed to one or more
of the following mailing lists:

  vpim@lists.neystadt.org
  ietf-fax@imc.org
  receipt@cs.utk.edu

To unsubscribe, try sending a message to:

  vpn-request@lists.neystadt.org
  ietf-fax-request@imc.org
  receipt-request@cs.utk.edu

with the word "unsubscribe" in the body of
your message.  If that doesn't do it, please
send me email directly (do not do a reply-all)
and I'll attempt to help you unsubscribe.

-d

> -----Original Message-----
> From: Jason McCurry [mailto:jasonm@speakeasy.org]
> Sent: Monday, August 27, 2001 5:16 PM
> To: Dan Wing; Vaudreuil, Greg M (Greg); receipt@cs.utk.edu
> Cc: vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: RE: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
>
>
> I'm not sure what you guys are talking about, or even how I got onto this
> list? Can whoever is in charge of this make sure jasonm@speakeasy.org is
> removed from whatever list is making me get these?
>
> Thanks,
>
> Jason McCurry
>
>
> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Monday, August 27, 2001 3:20 PM
> To: Vaudreuil, Greg M (Greg); receipt@cs.utk.edu
> Cc: vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: RE: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
>
>
> Greg,
>
> Thanks for forwarding this.
>
> > The following ID announcement is for a revision to the MDN specification
> in
> > preparation for Draft Standard.  Please note:  Many seemingly
> unimplemented
> > dispositions and all disposition modifiers have been removed.
>
> The ABNF in section 3.2.6 seems to still list the disposition modifiers.
>
> > If someone
> > can name TWO interoperable implementations of any of the deleted
> > dispositions or disposition modifiers, I will be happy to add them
> > back into the document.
> >
> > Note that the requirements for draft standard are explicit that
> > all features
> > and options need to have at least two, interoperable implementations.  If
> > they are still useful, the unimplemented dispositions deleted from this
> > document may be standardized at a later date as an MDN extension.
> >
> > This document also adds an additional section for gateway advice.  The
> > previous document was silent about what to do when gatewaying a MDN
> request
> > into a foreign network.  Given that most email networks do not have a
> > separate disposition-notification-to: recipient, that was a bit of an
> > oversight.
>
> Section 8.3 has a sentence which begins:
>
>   In other most email systems,
>
> which should be corrected.
>
> > Please review and send comments.  It is my hope that we can quickly
> advance
> > this to Draft Standard.
>
> Section 3.2.2 and the 'Status of this memo' section both seem to be missing
> some runoff commands to format the text correctly.
>
> -d
>
>
>



From owner-ietf-fax@mail.imc.org  Mon Aug 27 21:29:08 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05858
	for <fax-archive@odin.ietf.org>; Mon, 27 Aug 2001 21:29:08 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7S0rwF01826
	for ietf-fax-bks; Mon, 27 Aug 2001 17:53:58 -0700 (PDT)
Received: from kings.mei.co.jp (kings.mei.co.jp [202.224.189.27])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7S0rvD01819
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 17:53:57 -0700 (PDT)
Received: by kings.mei.co.jp (8.11.4/3.7W) with ESMTP id f7S0lM719619;
	Tue, 28 Aug 2001 09:48:54 +0900 (JST)
Received: by dodgers.mei.co.jp (8.9.1/3.7W) with SMTP id JAA14479;
	Tue, 28 Aug 2001 09:47:21 +0900 (JST)
Received: from [133.185.137.6] by m-bb2.mgcs.mei.co.jp
          via smtpd (for [157.8.1.150]) with SMTP; 28 Aug 2001 00:47:21 UT
Received: from mlsv1.mgcs.mei.co.jp
	by mlsv0.mgcs.mei.co.jp (8.9.3/3.7W-HUB) with ESMTP id JAA05766;
	Tue, 28 Aug 2001 09:47:21 +0900 (JST)
Received: from mlsv2.rdmg.mgcs.mei.co.jp
	by mlsv1.mgcs.mei.co.jp (8.9.3/3.7W-MGCS) with ESMTP id JAA09055;
	Tue, 28 Aug 2001 09:47:20 +0900 (JST)
Received: from d23n59.rdmg.mgcs.mei.co.jp
	by mlsv2.rdmg.mgcs.mei.co.jp (8.9.3/3.7W-RDMG) with SMTP id JAA04843;
	Tue, 28 Aug 2001 09:47:19 +0900 (JST)
Message-Id: <200108280049.AA00100@d23n59.rdmg.mgcs.mei.co.jp>
From: "Toyoda, Kiyoshi" <ktoyoda@rdmg.mgcs.mei.co.jp>
Date: Tue, 28 Aug 2001 09:49:50 +0900
To: gregv@lucent.com
Cc: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>,
        "'Dan Wing'" <dwing@cisco.com>,
        Hiroshi Tamura <tamura@toda.ricoh.co.jp>, receipt@cs.utk.edu,
        vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: Re: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
In-Reply-To: <51B8ABCE456FD111899900805F6FD6EE067A3575@mercury.ADOC.xerox.com>
References: <51B8ABCE456FD111899900805F6FD6EE067A3575@mercury.ADOC.xerox.com>
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.12
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


McIntyre, Lloyd wrote:
>
>My understanding is that the "dispatched" feature may be retained if
>information can be provided to verify that there are interoperable
>implementations.
>Tamura-san is it possible to have two or more manufacturers document
>interoperability of sending and receiving MDN with the dispatched feature?

Yes, I have the same understanding as McIntyre-san.
We implemented dispached feature in our prototype machine and I know other 
implementaions. So, I would like add the feature back into the document.

We implemented as below.

"dispatched" without modifiers when succesfully 
decoding the received TIFF-FX file

"processed/error"  or "processed/warning" in the case of the failure.


>
>Lloyd
>
>> -----Original Message-----
>> From: Dan Wing [mailto:dwing@cisco.com]
>> Sent: Monday, August 27, 2001 4:22 PM
>> To: Hiroshi Tamura; gregv@lucent.com
>> Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
>> Subject: RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
>> 
>> 
>> 
>> > > Note that the requirements for draft standard are explicit that
>> > all features
>> > > and options need to have at least two, interoperable 
>> implementations.  If
>> > > they are still useful, the unimplemented dispositions 
>> deleted from this
>> > > document may be standardized at a later date as an MDN extension.
>> >
>> > I do not read all, but I say,
>> >
>> > Some Ifax devices already use:
>> > "dispatched" or "processed" without modifiers
>> >   when succesfully decoding the received TIFF-FX file
>> > "processed/error" in the case of the failure.
>> 
>> Those devices will remain compliant with the Proposed 
>> Standard RFC2298,
>> but won't be compliant with the Draft Standard that Greg is authoring.
>> 
>> 
>> As soon as Greg's document becomes an RFC, I'll ask our development
>> group here in Cisco to bring our implementation in line with his
>> new Draft Standard.
>> 


Kiyoshi Toyoda


From owner-ietf-fax@mail.imc.org  Mon Aug 27 23:10:29 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09358
	for <fax-archive@odin.ietf.org>; Mon, 27 Aug 2001 23:10:28 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7S2PsU12354
	for ietf-fax-bks; Mon, 27 Aug 2001 19:25:54 -0700 (PDT)
Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7S2PqD12348
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 19:25:52 -0700 (PDT)
Received: from dns.maillennium.att.com ([135.25.114.99])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id f7S2PoV07445
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 22:25:50 -0400 (EDT)
Received: from att.com ([135.210.75.49])
          by maillennium.att.com (labmail) with SMTP
          id <2001082802254809900rl4cve>
          (Authid: tony@maillennium.att.com);
          Tue, 28 Aug 2001 02:25:48 +0000
Message-ID: <3B8B00CD.7B053A1@att.com>
Date: Mon, 27 Aug 2001 22:24:13 -0400
From: Tony Hansen <tony@att.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
CC: receipt@cs.utk.edu, vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
References: <51B8ABCE456FD111899900805F6FD6EE067A3575@mercury.ADOC.xerox.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Absolutely. If there ARE two (or more) implementations of anything we
removed, we'll put them back in to the updated MDN document.

So, just let us know of the implementations.

	Tony Hansen
	tony@att.com

"McIntyre, Lloyd" wrote:
> 
> My understanding is that the "dispatched" feature may be retained if
> information can be provided to verify that there are interoperable
> implementations.
> Tamura-san is it possible to have two or more manufacturers document
> interoperability of sending and receiving MDN with the dispatched feature?
> 
> Lloyd
> 
> > -----Original Message-----
> > From: Dan Wing [mailto:dwing@cisco.com]
> > Sent: Monday, August 27, 2001 4:22 PM
> > To: Hiroshi Tamura; gregv@lucent.com
> > Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> > Subject: RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> >
> >
> >
> > > > Note that the requirements for draft standard are explicit that
> > > all features
> > > > and options need to have at least two, interoperable
> > implementations.  If
> > > > they are still useful, the unimplemented dispositions
> > deleted from this
> > > > document may be standardized at a later date as an MDN extension.
> > >
> > > I do not read all, but I say,
> > >
> > > Some Ifax devices already use:
> > > "dispatched" or "processed" without modifiers
> > >   when succesfully decoding the received TIFF-FX file
> > > "processed/error" in the case of the failure.
> >
> > Those devices will remain compliant with the Proposed
> > Standard RFC2298,
> > but won't be compliant with the Draft Standard that Greg is authoring.
> >
> >
> > As soon as Greg's document becomes an RFC, I'll ask our development
> > group here in Cisco to bring our implementation in line with his
> > new Draft Standard.
> >
> > -d
> >
> ----------------------------------------------------------
> This message was sent to you, since you are subscribed to
> vpim@lists.neystadt.org. You can manage your subscription at
> http://www.neystadt.org/cgi-bin/majordomo


From owner-ietf-fax@mail.imc.org  Tue Aug 28 01:03:11 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA10961
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 01:03:10 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7S4MAp29755
	for ietf-fax-bks; Mon, 27 Aug 2001 21:22:10 -0700 (PDT)
Received: from mx.toshibatec.co.jp (mx.toshibatec.co.jp [202.215.2.15])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7S4M8D29751
	for <ietf-fax@imc.org>; Mon, 27 Aug 2001 21:22:09 -0700 (PDT)
Received: from cn.toshibatec.co.jp by mx.toshibatec.co.jp (8.8.8+Sun/3.6W TEC mailserver) id NAA29410; Tue, 28 Aug 2001 13:11:47 +0900 (JST)
Received: from president.rdl.toshibatec.co.jp by cn.toshibatec.co.jp (SMI-8.6/3.5W TEC master mailserver [99/10/07 13:34]) id NAA25752; Tue, 28 Aug 2001 13:06:11 +0900
Received: from t21012412 
Message-ID: <009001c12f77$73b5ea00$8fcc459d@t21012412>
Reply-To: "Ryuji Iwazaki" <iwa@rdl.toshibatec.co.jp>
From: "Ryuji Iwazaki" <iwa@rdl.toshibatec.co.jp>
To: "Tony Hansen" <tony@att.com>,
        "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
Cc: <receipt@cs.utk.edu>, <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
References: <51B8ABCE456FD111899900805F6FD6EE067A3575@mercury.ADOC.xerox.com> <3B8B00CD.7B053A1@att.com>
Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Tue, 28 Aug 2001 13:11:02 +0900
Organization: TOSHIBA TEC CORPORATION
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


> Absolutely. If there ARE two (or more) implementations of anything we
> removed, we'll put them back in to the updated MDN document.
>
> So, just let us know of the implementations.
>
> Tony Hansen
> tony@att.com
>

TOSHIBA TEC has the Internet Fax products which implement the "dispatched"
feature.
We implemented same as MGCS.

"dispatched" without modifiers when succesfully
decoding the received TIFF-FX file

"processed/error"  or "processed/warning" in the case of the failure.


Regards,

Ryuji Iwazaki
TOSHIBA TEC Corporation




From owner-ietf-fax@mail.imc.org  Tue Aug 28 12:16:07 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14355
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 12:16:07 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SFgxA28691
	for ietf-fax-bks; Tue, 28 Aug 2001 08:42:59 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SFgwD28685
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 08:42:58 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f7SFhDH20342;
	Tue, 28 Aug 2001 08:43:13 -0700 (PDT)
Received: from DWINGW2K (dwings-dsl4.cisco.com [10.19.89.165])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAJ06068;
	Tue, 28 Aug 2001 08:42:53 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "Vaudreuil, Greg M \(Greg\)" <gregv@lucent.com>,
        "Tony Hansen" <tony@att.com>,
        "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
Cc: <receipt@cs.utk.edu>, <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
Subject: RE: Error, failure, warning fields.
Date: Tue, 28 Aug 2001 08:42:53 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGAEAIEIAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <0096D8500C92D211BAEB0008C7F4906C04D02907@co7040exch002u.milehi.lucent.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


I just checked our implementation, and we transmit an MDN that
says either "dispatched" or "processed/error".  The "/error" is a
disposition modifier.

On reception of an MDN we don't parse at all -- we merely relay up to two
lines of text to the fax machine and leave it to the user to decipher
the meaning.

So I don't care if we eliminate the disposition-modifier field.

If it's retained, I would certainly like the list of disposition-
modifiers reduced to just "error" and "warning".

-d

> -----Original Message-----
> From: Vaudreuil, Greg M (Greg) [mailto:gregv@lucent.com]
> Sent: Tuesday, August 28, 2001 8:03 AM
> To: Tony Hansen; McIntyre, Lloyd
> Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: MDN: Error, failure, warning fields.
>
>
>
> Are there any implementations of the error, warning, or failure fields?  I
> have not personally seen any or heard of any.  Unless someone can identify
> two or more implementations of these fields, I will delete them.
>
> These fields are distinct from the disposition modifiers discussed in the
> attached message.
>
> Note also that the intent of these fields is to provide additional textual
> description of the MDN exception case.  It seems this purpose can be met by
> supplying X- extension fields or text in the first part of the
> multipart/report structure.
>
> Greg V.
>
> -----Original Message-----
> From: Tony Hansen [mailto:tony@att.com]
> Sent: Monday, August 27, 2001 9:24 PM
> To: McIntyre, Lloyd
> Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
>
>
> Absolutely. If there ARE two (or more) implementations of anything we
> removed, we'll put them back in to the updated MDN document.
>
> So, just let us know of the implementations.
>
> 	Tony Hansen
> 	tony@att.com
>
> "McIntyre, Lloyd" wrote:
> >
> > My understanding is that the "dispatched" feature may be retained if
> > information can be provided to verify that there are interoperable
> > implementations.
> > Tamura-san is it possible to have two or more manufacturers document
> > interoperability of sending and receiving MDN with the
> dispatched feature?
> >
> > Lloyd
> >
> > > -----Original Message-----
> > > From: Dan Wing [mailto:dwing@cisco.com]
> > > Sent: Monday, August 27, 2001 4:22 PM
> > > To: Hiroshi Tamura; gregv@lucent.com
> > > Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> > > Subject: RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> > >
> > >
> > >
> > > > > Note that the requirements for draft standard are explicit that
> > > > all features
> > > > > and options need to have at least two, interoperable
> > > implementations.  If
> > > > > they are still useful, the unimplemented dispositions
> > > deleted from this
> > > > > document may be standardized at a later date as an MDN extension.
> > > >
> > > > I do not read all, but I say,
> > > >
> > > > Some Ifax devices already use:
> > > > "dispatched" or "processed" without modifiers
> > > >   when succesfully decoding the received TIFF-FX file
> > > > "processed/error" in the case of the failure.
> > >
> > > Those devices will remain compliant with the Proposed
> > > Standard RFC2298,
> > > but won't be compliant with the Draft Standard that Greg is authoring.
> > >
> > >
> > > As soon as Greg's document becomes an RFC, I'll ask our development
> > > group here in Cisco to bring our implementation in line with his
> > > new Draft Standard.
> > >
> > > -d
> > >
> > ----------------------------------------------------------
> > This message was sent to you, since you are subscribed to
> > vpim@lists.neystadt.org. You can manage your subscription at
> > http://www.neystadt.org/cgi-bin/majordomo
> ----------------------------------------------------------
> This message was sent to you, since you are subscribed to
> vpim@lists.neystadt.org. You can manage your subscription at
> http://www.neystadt.org/cgi-bin/majordomo



From owner-ietf-fax@mail.imc.org  Tue Aug 28 12:16:54 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14402
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 12:16:54 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SFcXs27710
	for ietf-fax-bks; Tue, 28 Aug 2001 08:38:33 -0700 (PDT)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SFcVD27701
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 08:38:31 -0700 (PDT)
Received: from co7040exch001p.wins.lucent.com (h135-39-1-40.lucent.com [135.39.1.40])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id f7SF3Xe03631
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 11:03:33 -0400 (EDT)
Received: by co7040exch001p.milehi.lucent.com with Internet Mail Service (5.5.2650.21)
	id <PGJ9RK0G>; Tue, 28 Aug 2001 09:03:23 -0600
Message-ID: <0096D8500C92D211BAEB0008C7F4906C04D02907@co7040exch002u.milehi.lucent.com>
From: "Vaudreuil, Greg M (Greg)" <gregv@lucent.com>
To: Tony Hansen <tony@att.com>,
        "McIntyre, Lloyd"
	 <Lloyd.McIntyre@pahv.xerox.com>
Cc: receipt@cs.utk.edu, vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: MDN: Error, failure, warning fields.
Date: Tue, 28 Aug 2001 09:03:19 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>



Are there any implementations of the error, warning, or failure fields?  I
have not personally seen any or heard of any.  Unless someone can identify
two or more implementations of these fields, I will delete them.

These fields are distinct from the disposition modifiers discussed in the
attached message.

Note also that the intent of these fields is to provide additional textual
description of the MDN exception case.  It seems this purpose can be met by
supplying X- extension fields or text in the first part of the
multipart/report structure.

Greg V.

-----Original Message-----
From: Tony Hansen [mailto:tony@att.com]
Sent: Monday, August 27, 2001 9:24 PM
To: McIntyre, Lloyd
Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt


Absolutely. If there ARE two (or more) implementations of anything we
removed, we'll put them back in to the updated MDN document.

So, just let us know of the implementations.

	Tony Hansen
	tony@att.com

"McIntyre, Lloyd" wrote:
> 
> My understanding is that the "dispatched" feature may be retained if
> information can be provided to verify that there are interoperable
> implementations.
> Tamura-san is it possible to have two or more manufacturers document
> interoperability of sending and receiving MDN with the dispatched feature?
> 
> Lloyd
> 
> > -----Original Message-----
> > From: Dan Wing [mailto:dwing@cisco.com]
> > Sent: Monday, August 27, 2001 4:22 PM
> > To: Hiroshi Tamura; gregv@lucent.com
> > Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> > Subject: RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> >
> >
> >
> > > > Note that the requirements for draft standard are explicit that
> > > all features
> > > > and options need to have at least two, interoperable
> > implementations.  If
> > > > they are still useful, the unimplemented dispositions
> > deleted from this
> > > > document may be standardized at a later date as an MDN extension.
> > >
> > > I do not read all, but I say,
> > >
> > > Some Ifax devices already use:
> > > "dispatched" or "processed" without modifiers
> > >   when succesfully decoding the received TIFF-FX file
> > > "processed/error" in the case of the failure.
> >
> > Those devices will remain compliant with the Proposed
> > Standard RFC2298,
> > but won't be compliant with the Draft Standard that Greg is authoring.
> >
> >
> > As soon as Greg's document becomes an RFC, I'll ask our development
> > group here in Cisco to bring our implementation in line with his
> > new Draft Standard.
> >
> > -d
> >
> ----------------------------------------------------------
> This message was sent to you, since you are subscribed to
> vpim@lists.neystadt.org. You can manage your subscription at
> http://www.neystadt.org/cgi-bin/majordomo
----------------------------------------------------------
This message was sent to you, since you are subscribed to
vpim@lists.neystadt.org. You can manage your subscription at
http://www.neystadt.org/cgi-bin/majordomo


From owner-ietf-fax@mail.imc.org  Tue Aug 28 12:45:46 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15500
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 12:45:45 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SG8la01920
	for ietf-fax-bks; Tue, 28 Aug 2001 09:08:47 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SG8kD01915
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 09:08:46 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id f7SG91H08151;
	Tue, 28 Aug 2001 09:09:01 -0700 (PDT)
Received: from DWINGW2K (dwings-dsl4.cisco.com [10.19.89.165])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAJ06686;
	Tue, 28 Aug 2001 09:08:41 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "Vaudreuil, Greg M \(Greg\)" <gregv@lucent.com>,
        "Tony Hansen" <tony@att.com>,
        "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
Cc: <receipt@cs.utk.edu>, <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
Subject: RE: Error, failure, warning fields.
Date: Tue, 28 Aug 2001 09:08:40 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGAEAMEIAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <0096D8500C92D211BAEB0008C7F4906C04D02907@co7040exch002u.milehi.lucent.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Greg,

> Are there any implementations of the error, warning, or failure fields?  I
> have not personally seen any or heard of any.  Unless someone can identify
> two or more implementations of these fields, I will delete them.

Yes, we use the Error field only in this case:

        sprintf(buffer + strlen(buffer),
                "Disposition: automatic-action/MDN-sent-automatically;
%s\r\n",
                level == RECIPIENT_LEVEL_OK ?
"dispatched":"processed/error");
        if (level != RECIPIENT_LEVEL_OK) {
            sprintf(buffer + strlen(buffer), "Error: %s %s\r\n",
                    statusCode, messageStr);
        }

"level" would be unequal to RECIPIENT_LEVEL_OK if the TIFF reader or BASE64
decoder reported an error to the SMTP server.  The value of statusCode
and messageStr are set by the TIFF reader or BASE64 decoder to help diagnose
the problem.

-d

> These fields are distinct from the disposition modifiers discussed in the
> attached message.
>
> Note also that the intent of these fields is to provide additional textual
> description of the MDN exception case.  It seems this purpose can be met by
> supplying X- extension fields or text in the first part of the
> multipart/report structure.
>
> Greg V.
>
> -----Original Message-----
> From: Tony Hansen [mailto:tony@att.com]
> Sent: Monday, August 27, 2001 9:24 PM
> To: McIntyre, Lloyd
> Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
>
>
> Absolutely. If there ARE two (or more) implementations of anything we
> removed, we'll put them back in to the updated MDN document.
>
> So, just let us know of the implementations.
>
> 	Tony Hansen
> 	tony@att.com
>
> "McIntyre, Lloyd" wrote:
> >
> > My understanding is that the "dispatched" feature may be retained if
> > information can be provided to verify that there are interoperable
> > implementations.
> > Tamura-san is it possible to have two or more manufacturers document
> > interoperability of sending and receiving MDN with the
> dispatched feature?
> >
> > Lloyd
> >
> > > -----Original Message-----
> > > From: Dan Wing [mailto:dwing@cisco.com]
> > > Sent: Monday, August 27, 2001 4:22 PM
> > > To: Hiroshi Tamura; gregv@lucent.com
> > > Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> > > Subject: RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> > >
> > >
> > >
> > > > > Note that the requirements for draft standard are explicit that
> > > > all features
> > > > > and options need to have at least two, interoperable
> > > implementations.  If
> > > > > they are still useful, the unimplemented dispositions
> > > deleted from this
> > > > > document may be standardized at a later date as an MDN extension.
> > > >
> > > > I do not read all, but I say,
> > > >
> > > > Some Ifax devices already use:
> > > > "dispatched" or "processed" without modifiers
> > > >   when succesfully decoding the received TIFF-FX file
> > > > "processed/error" in the case of the failure.
> > >
> > > Those devices will remain compliant with the Proposed
> > > Standard RFC2298,
> > > but won't be compliant with the Draft Standard that Greg is authoring.
> > >
> > >
> > > As soon as Greg's document becomes an RFC, I'll ask our development
> > > group here in Cisco to bring our implementation in line with his
> > > new Draft Standard.
> > >
> > > -d
> > >
> > ----------------------------------------------------------
> > This message was sent to you, since you are subscribed to
> > vpim@lists.neystadt.org. You can manage your subscription at
> > http://www.neystadt.org/cgi-bin/majordomo
> ----------------------------------------------------------
> This message was sent to you, since you are subscribed to
> vpim@lists.neystadt.org. You can manage your subscription at
> http://www.neystadt.org/cgi-bin/majordomo



From owner-ietf-fax@mail.imc.org  Tue Aug 28 13:48:19 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17008
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 13:48:19 -0400 (EDT)
Received: by above.proper.com (8.11.6/8.11.3) id f7SHAvi03408
	for ietf-fax-bks; Tue, 28 Aug 2001 10:10:57 -0700 (PDT)
Received: from umbriel.eastgw.xerox.com (umbriel.xerox.com [208.140.33.26])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SHAtD03404
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 10:10:55 -0700 (PDT)
Received: from godzilla.ADOC.xerox.com (godzilla.ADOC.xerox.com [13.242.128.10])
	by umbriel.eastgw.xerox.com (8.9.3/8.9.3) with ESMTP id NAA26413;
	Tue, 28 Aug 2001 13:10:47 -0400 (EDT)
Received: from mercury.adoc.xerox.com (mercury [13.242.100.20])
	by godzilla.ADOC.xerox.com (8.8.8+Sun/8.8.8/ADOC-HUB-1.7) with ESMTP id KAA00576;
	Tue, 28 Aug 2001 10:10:53 -0700 (PDT)
Received: by mercury.ADOC.xerox.com with Internet Mail Service (5.5.2653.19)
	id <RLRRMNFS>; Tue, 28 Aug 2001 10:10:52 -0700
Message-ID: <51B8ABCE456FD111899900805F6FD6EE067A357F@mercury.ADOC.xerox.com>
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
To: "'Shibata Tetsuya'" <shibata@ns1.nara.sharp.co.jp>,
        "'tony@att.com'"
	 <tony@att.com>,
        "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
Cc: "'receipt@cs.utk.edu'" <receipt@cs.utk.edu>,
        "'vpim@lists.neystadt.org'" <vpim@lists.neystadt.org>,
        "'ietf-fax@imc.org'" <ietf-fax@imc.org>
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Tue, 28 Aug 2001 10:10:52 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-2022-jp"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


I would like to add to the voices by expressing that Xerox products in the
field do implement the dispatched feature as described by others.

Next steps is for us to get together and conduct a simple series of
sends/receives between our implementations and document the outcome (e.g.
successful/unsuccessful exchange, interpretation and identity of test
partners). This documentation should then be provided to the WG chair(s) who
would submit it to the Area Director with the protocol action request.

Shibata, Iwazaki and Toyoda-san please let me know if you desire to make
plans for testing. 

Lloyd

> -----Original Message-----
> From: Shibata Tetsuya [mailto:shibata@ns1.nara.sharp.co.jp]
> Sent: Tuesday, August 28, 2001 4:27 AM
> To: 'tony@att.com'; 'Lloyd.McIntyre@pahv.xerox.com'
> Cc: 'receipt@cs.utk.edu'; 'vpim@lists.neystadt.org'; 
> 'ietf-fax@imc.org'
> Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> 
> 
> I am a developer working at SHARP.
> 
>  > -----Original Message-----
>  > From: Tony Hansen [mailto:tony@att.com]
>  > Sent: Tuesday, August 28, 2001 11:24 AM
>  > To: McIntyre, Lloyd
>  > Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
>  > Subject: Re: [VPIM] RE: FW: I-D 
> ACTION:draft-vaudreuil-mdnbis-00.txt
>  > 
>  > 
>  > 
>  > Absolutely. If there ARE two (or more) implementations of 
> anything we
>  > removed, we'll put them back in to the updated MDN document.
>  > 
>  > So, just let us know of the implementations.
>  > 
>  > 	Tony Hansen
>  > 	tony@att.com
>  > 
>  > "McIntyre, Lloyd" wrote:
> 
> We have already developed the prototype which built in the 
> "dispatched" feature.
> 
> We implemented almost the same as MGCS & TOSHIBA TEC.
> 
> "dispatched" without modifiers when succesfully decoding the 
> received TIFF-FX file.
> "processed/error" in the case of the failure.
> 
> 
> Regards,
> 
>  Tetsuya Shibata
>  SHARP CORPORATION
> 


From owner-ietf-fax@mail.imc.org  Tue Aug 28 14:19:09 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17699
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 14:19:08 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SHhKx04153
	for ietf-fax-bks; Tue, 28 Aug 2001 10:43:20 -0700 (PDT)
Received: from umbriel.eastgw.xerox.com (umbriel.xerox.com [208.140.33.26])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SHhJD04149
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 10:43:19 -0700 (PDT)
Received: from godzilla.ADOC.xerox.com (godzilla.ADOC.xerox.com [13.242.128.10])
	by umbriel.eastgw.xerox.com (8.9.3/8.9.3) with ESMTP id NAA16796;
	Tue, 28 Aug 2001 13:43:11 -0400 (EDT)
Received: from mercury.adoc.xerox.com (mercury [13.242.100.20])
	by godzilla.ADOC.xerox.com (8.8.8+Sun/8.8.8/ADOC-HUB-1.7) with ESMTP id KAA01291;
	Tue, 28 Aug 2001 10:43:17 -0700 (PDT)
Received: by mercury.ADOC.xerox.com with Internet Mail Service (5.5.2653.19)
	id <RLRRMNRB>; Tue, 28 Aug 2001 10:43:17 -0700
Message-ID: <51B8ABCE456FD111899900805F6FD6EE067A3581@mercury.ADOC.xerox.com>
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
To: "'tony@att.com'" <tony@att.com>
Cc: "'receipt@cs.utk.edu'" <receipt@cs.utk.edu>,
        "'vpim@lists.neystadt.org'" <vpim@lists.neystadt.org>,
        "'ietf-fax@imc.org'" <ietf-fax@imc.org>
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Tue, 28 Aug 2001 10:43:16 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-2022-jp"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


Please also note that the fax Implementers Guide, currently under
Informational Standard Last Call, recommends and provides examples for use
of disposition-modifiers.

See 4.4.1.2 Disposition-Type and body of message in MDN
and 
4.4.4.2 Failure Case Example.

Lloyd

> -----Original Message-----
> From: Shibata Tetsuya [mailto:shibata@ns1.nara.sharp.co.jp]
> Sent: Tuesday, August 28, 2001 4:27 AM
> To: 'tony@att.com'; 'Lloyd.McIntyre@pahv.xerox.com'
> Cc: 'receipt@cs.utk.edu'; 'vpim@lists.neystadt.org'; 
> 'ietf-fax@imc.org'
> Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> 
> 
> I am a developer working at SHARP.
> 
>  > -----Original Message-----
>  > From: Tony Hansen [mailto:tony@att.com]
>  > Sent: Tuesday, August 28, 2001 11:24 AM
>  > To: McIntyre, Lloyd
>  > Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
>  > Subject: Re: [VPIM] RE: FW: I-D 
> ACTION:draft-vaudreuil-mdnbis-00.txt
>  > 
>  > 
>  > 
>  > Absolutely. If there ARE two (or more) implementations of 
> anything we
>  > removed, we'll put them back in to the updated MDN document.
>  > 
>  > So, just let us know of the implementations.
>  > 
>  > 	Tony Hansen
>  > 	tony@att.com
>  > 
>  > "McIntyre, Lloyd" wrote:
> 
> We have already developed the prototype which built in the 
> "dispatched" feature.
> 
> We implemented almost the same as MGCS & TOSHIBA TEC.
> 
> "dispatched" without modifiers when succesfully decoding the 
> received TIFF-FX file.
> "processed/error" in the case of the failure.
> 
> 
> Regards,
> 
>  Tetsuya Shibata
>  SHARP CORPORATION
> 


From owner-ietf-fax@mail.imc.org  Tue Aug 28 14:39:56 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18281
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 14:39:56 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SI5i904567
	for ietf-fax-bks; Tue, 28 Aug 2001 11:05:44 -0700 (PDT)
Received: from kcmso1.proxy.att.com (kcmso1.att.com [192.128.133.69])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SI5gD04563
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 11:05:42 -0700 (PDT)
Received: from dns.maillennium.att.com ([135.25.114.99])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id f7SI5XV26591
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 14:05:39 -0400 (EDT)
Received: from att.com ([135.210.75.193])
          by maillennium.att.com (labmail) with SMTP
          id <2001082818053209900rl4vje>
          (Authid: tony@maillennium.att.com);
          Tue, 28 Aug 2001 18:05:33 +0000
Message-ID: <3B8BDD0A.E50712@att.com>
Date: Tue, 28 Aug 2001 14:03:54 -0400
From: Tony Hansen <tony@att.com>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "'ietf-fax@imc.org'" <ietf-fax@imc.org>
Subject: draft-ietf-fax-implementers-guide-07.txt
References: <51B8ABCE456FD111899900805F6FD6EE067A3581@mercury.ADOC.xerox.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


The examples in draft-ietf-fax-implementers-guide-07.txt spell the
arguments in the MDN Disposition: headers incorrectly. In particular,
MDN-send-automatically should be MDN-sent-automatically.

	Tony Hansen
	tony@att.com


From owner-ietf-fax@mail.imc.org  Tue Aug 28 16:52:23 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21212
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 16:52:23 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SK8HE06969
	for ietf-fax-bks; Tue, 28 Aug 2001 13:08:17 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SK8GD06965
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 13:08:16 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f7SK8Il14035;
	Tue, 28 Aug 2001 13:08:18 -0700 (PDT)
Received: from DWINGW2K (dhcp-128-107-139-165.cisco.com [128.107.139.165])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAJ14340;
	Tue, 28 Aug 2001 13:08:12 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>,
        "'Shibata Tetsuya'" <shibata@ns1.nara.sharp.co.jp>, <tony@att.com>
Cc: <receipt@cs.utk.edu>, <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Tue, 28 Aug 2001 13:08:12 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGAECHEIAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <51B8ABCE456FD111899900805F6FD6EE067A357F@mercury.ADOC.xerox.com>
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Note we need vendors to both send _and_ receive the various 
permutations.  If all implementations only send and do not parse
or validate or do something on receipt, it doesn't pass muster
for Draft Standard.

-d

> -----Original Message-----
> From: McIntyre, Lloyd [mailto:Lloyd.McIntyre@pahv.xerox.com]
> Sent: Tuesday, August 28, 2001 10:11 AM
> To: 'Shibata Tetsuya'; 'tony@att.com'; McIntyre, Lloyd
> Cc: 'receipt@cs.utk.edu'; 'vpim@lists.neystadt.org'; 'ietf-fax@imc.org'
> Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> 
> 
> I would like to add to the voices by expressing that Xerox products in the
> field do implement the dispatched feature as described by others.
> 
> Next steps is for us to get together and conduct a simple series of
> sends/receives between our implementations and document the outcome (e.g.
> successful/unsuccessful exchange, interpretation and identity of test
> partners). This documentation should then be provided to the WG 
> chair(s) who
> would submit it to the Area Director with the protocol action request.
> 
> Shibata, Iwazaki and Toyoda-san please let me know if you desire to make
> plans for testing. 
> 
> Lloyd
> 
> > -----Original Message-----
> > From: Shibata Tetsuya [mailto:shibata@ns1.nara.sharp.co.jp]
> > Sent: Tuesday, August 28, 2001 4:27 AM
> > To: 'tony@att.com'; 'Lloyd.McIntyre@pahv.xerox.com'
> > Cc: 'receipt@cs.utk.edu'; 'vpim@lists.neystadt.org'; 
> > 'ietf-fax@imc.org'
> > Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> > 
> > 
> > I am a developer working at SHARP.
> > 
> >  > -----Original Message-----
> >  > From: Tony Hansen [mailto:tony@att.com]
> >  > Sent: Tuesday, August 28, 2001 11:24 AM
> >  > To: McIntyre, Lloyd
> >  > Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> >  > Subject: Re: [VPIM] RE: FW: I-D 
> > ACTION:draft-vaudreuil-mdnbis-00.txt
> >  > 
> >  > 
> >  > 
> >  > Absolutely. If there ARE two (or more) implementations of 
> > anything we
> >  > removed, we'll put them back in to the updated MDN document.
> >  > 
> >  > So, just let us know of the implementations.
> >  > 
> >  > 	Tony Hansen
> >  > 	tony@att.com
> >  > 
> >  > "McIntyre, Lloyd" wrote:
> > 
> > We have already developed the prototype which built in the 
> > "dispatched" feature.
> > 
> > We implemented almost the same as MGCS & TOSHIBA TEC.
> > 
> > "dispatched" without modifiers when succesfully decoding the 
> > received TIFF-FX file.
> > "processed/error" in the case of the failure.
> > 
> > 
> > Regards,
> > 
> >  Tetsuya Shibata
> >  SHARP CORPORATION
> > 


From owner-ietf-fax@mail.imc.org  Tue Aug 28 16:53:42 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21231
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 16:53:41 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SKHB707121
	for ietf-fax-bks; Tue, 28 Aug 2001 13:17:11 -0700 (PDT)
Received: from episteme-software.com (champdsl-25.mcleodusa.net [216.43.25.66] (may be forged))
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SKH7D07117
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 13:17:08 -0700 (PDT)
Received: from [216.43.25.67] (216.43.25.67) by episteme-software.com with
 ESMTP (Eudora Internet Mail Server 3.1b1);
 Tue, 28 Aug 2001 15:16:58 -0500
Mime-Version: 1.0
X-Sender: resnick@resnick1.qualcomm.com (Unverified)
Message-Id: <a05100301b7b1ab547fdc@[216.43.25.67]>
In-Reply-To: <EOEBIJPEADOODFNEJPEGAECHEIAA.dwing@cisco.com>
References: <EOEBIJPEADOODFNEJPEGAECHEIAA.dwing@cisco.com>
X-Mailer: Eudora [Macintosh version 5.1a1-12.00]
Date: Tue, 28 Aug 2001 15:16:57 -0500
To: "Dan Wing" <dwing@cisco.com>
From: Pete Resnick <presnick@Qualcomm.Com>
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Cc: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>,
        "'Shibata Tetsuya'" <shibata@ns1.nara.sharp.co.jp>, <tony@att.com>,
        <receipt@cs.utk.edu>, <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


On 8/28/01 at 1:08 PM -0700, Dan Wing wrote:

>Note we need vendors to both send _and_ receive the various
>permutations.  If all implementations only send and do not parse
>or validate or do something on receipt, it doesn't pass muster
>for Draft Standard.

Eudora (certainly on the Mac and I believe also on Windows) displays 
the disposition values to the user as text. Now, it's not doing any 
real parsing; it's just displaying the contents of the 
message/disposition-notification part as text. Shouldn't that be 
enough to be a "receiving" client?

pr
-- 
Pete Resnick <mailto:presnick@qualcomm.com>
QUALCOMM Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102


From owner-ietf-fax@mail.imc.org  Tue Aug 28 17:16:01 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21685
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 17:16:01 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SKbxd07453
	for ietf-fax-bks; Tue, 28 Aug 2001 13:37:59 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SKbwD07449
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 13:37:58 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id f7SKbql08974;
	Tue, 28 Aug 2001 13:37:52 -0700 (PDT)
Received: from DWINGW2K (dhcp-128-107-139-165.cisco.com [128.107.139.165])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAJ15263;
	Tue, 28 Aug 2001 13:37:51 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "Pete Resnick" <presnick@Qualcomm.Com>
Cc: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>,
        "'Shibata Tetsuya'" <shibata@ns1.nara.sharp.co.jp>, <tony@att.com>,
        <receipt@cs.utk.edu>, <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Tue, 28 Aug 2001 13:37:51 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGEECLEIAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <a05100301b7b1ab547fdc@[216.43.25.67]>
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


> >Note we need vendors to both send _and_ receive the various
> >permutations.  If all implementations only send and do not parse
> >or validate or do something on receipt, it doesn't pass muster
> >for Draft Standard.
> 
> Eudora (certainly on the Mac and I believe also on Windows) displays 
> the disposition values to the user as text. Now, it's not doing any 
> real parsing; it's just displaying the contents of the 
> message/disposition-notification part as text. Shouldn't that be 
> enough to be a "receiving" client?

Yes, good point.  We do the same, and expect the user to take some
action based on what they see.

-d



From owner-ietf-fax@mail.imc.org  Tue Aug 28 18:12:03 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22545
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 18:12:03 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SLaNk08555
	for ietf-fax-bks; Tue, 28 Aug 2001 14:36:23 -0700 (PDT)
Received: from umbriel.eastgw.xerox.com (umbriel.xerox.com [208.140.33.26])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SLaLD08551
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 14:36:21 -0700 (PDT)
Received: from godzilla.ADOC.xerox.com (godzilla.ADOC.xerox.com [13.242.128.10])
	by umbriel.eastgw.xerox.com (8.9.3/8.9.3) with ESMTP id RAA15983;
	Tue, 28 Aug 2001 17:36:14 -0400 (EDT)
Received: from mercury.adoc.xerox.com (mercury [13.242.100.20])
	by godzilla.ADOC.xerox.com (8.8.8+Sun/8.8.8/ADOC-HUB-1.7) with ESMTP id OAA06969;
	Tue, 28 Aug 2001 14:36:19 -0700 (PDT)
Received: by mercury.ADOC.xerox.com with Internet Mail Service (5.5.2653.19)
	id <RLRRMQX5>; Tue, 28 Aug 2001 14:36:19 -0700
Message-ID: <51B8ABCE456FD111899900805F6FD6EE067A3586@mercury.ADOC.xerox.com>
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
To: "'Dan Wing'" <dwing@cisco.com>,
        "McIntyre, Lloyd"
	 <Lloyd.McIntyre@pahv.xerox.com>,
        "'Shibata Tetsuya'"
	 <shibata@ns1.nara.sharp.co.jp>, tony@att.com
Cc: receipt@cs.utk.edu, vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Tue, 28 Aug 2001 14:36:16 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-2022-jp"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


Dan,
Your comments are consistent with my expectations.
We need to start planning for realization.

Lloyd

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Tuesday, August 28, 2001 1:08 PM
> To: McIntyre, Lloyd; 'Shibata Tetsuya'; tony@att.com
> Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> 
> 
> Note we need vendors to both send _and_ receive the various 
> permutations.  If all implementations only send and do not parse
> or validate or do something on receipt, it doesn't pass muster
> for Draft Standard.
> 
> -d
> 
> > -----Original Message-----
> > From: McIntyre, Lloyd [mailto:Lloyd.McIntyre@pahv.xerox.com]
> > Sent: Tuesday, August 28, 2001 10:11 AM
> > To: 'Shibata Tetsuya'; 'tony@att.com'; McIntyre, Lloyd
> > Cc: 'receipt@cs.utk.edu'; 'vpim@lists.neystadt.org'; 
> 'ietf-fax@imc.org'
> > Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> > 
> > 
> > I would like to add to the voices by expressing that Xerox 
> products in the
> > field do implement the dispatched feature as described by others.
> > 
> > Next steps is for us to get together and conduct a simple series of
> > sends/receives between our implementations and document the 
> outcome (e.g.
> > successful/unsuccessful exchange, interpretation and 
> identity of test
> > partners). This documentation should then be provided to the WG 
> > chair(s) who
> > would submit it to the Area Director with the protocol 
> action request.
> > 
> > Shibata, Iwazaki and Toyoda-san please let me know if you 
> desire to make
> > plans for testing. 
> > 
> > Lloyd
> > 
> > > -----Original Message-----
> > > From: Shibata Tetsuya [mailto:shibata@ns1.nara.sharp.co.jp]
> > > Sent: Tuesday, August 28, 2001 4:27 AM
> > > To: 'tony@att.com'; 'Lloyd.McIntyre@pahv.xerox.com'
> > > Cc: 'receipt@cs.utk.edu'; 'vpim@lists.neystadt.org'; 
> > > 'ietf-fax@imc.org'
> > > Subject: RE: [VPIM] RE: FW: I-D 
> ACTION:draft-vaudreuil-mdnbis-00.txt
> > > 
> > > 
> > > I am a developer working at SHARP.
> > > 
> > >  > -----Original Message-----
> > >  > From: Tony Hansen [mailto:tony@att.com]
> > >  > Sent: Tuesday, August 28, 2001 11:24 AM
> > >  > To: McIntyre, Lloyd
> > >  > Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; 
> ietf-fax@imc.org
> > >  > Subject: Re: [VPIM] RE: FW: I-D 
> > > ACTION:draft-vaudreuil-mdnbis-00.txt
> > >  > 
> > >  > 
> > >  > 
> > >  > Absolutely. If there ARE two (or more) implementations of 
> > > anything we
> > >  > removed, we'll put them back in to the updated MDN document.
> > >  > 
> > >  > So, just let us know of the implementations.
> > >  > 
> > >  > 	Tony Hansen
> > >  > 	tony@att.com
> > >  > 
> > >  > "McIntyre, Lloyd" wrote:
> > > 
> > > We have already developed the prototype which built in the 
> > > "dispatched" feature.
> > > 
> > > We implemented almost the same as MGCS & TOSHIBA TEC.
> > > 
> > > "dispatched" without modifiers when succesfully decoding the 
> > > received TIFF-FX file.
> > > "processed/error" in the case of the failure.
> > > 
> > > 
> > > Regards,
> > > 
> > >  Tetsuya Shibata
> > >  SHARP CORPORATION
> > > 
> 


From owner-ietf-fax@mail.imc.org  Tue Aug 28 18:34:10 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22857
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 18:34:10 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SLpYR08782
	for ietf-fax-bks; Tue, 28 Aug 2001 14:51:34 -0700 (PDT)
Received: from umbriel.eastgw.xerox.com (umbriel.xerox.com [208.140.33.26])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SLpXD08776
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 14:51:33 -0700 (PDT)
Received: from godzilla.ADOC.xerox.com (godzilla.ADOC.xerox.com [13.242.128.10])
	by umbriel.eastgw.xerox.com (8.9.3/8.9.3) with ESMTP id RAA22788;
	Tue, 28 Aug 2001 17:51:17 -0400 (EDT)
Received: from mercury.adoc.xerox.com (mercury [13.242.100.20])
	by godzilla.ADOC.xerox.com (8.8.8+Sun/8.8.8/ADOC-HUB-1.7) with ESMTP id OAA07270;
	Tue, 28 Aug 2001 14:51:22 -0700 (PDT)
Received: by mercury.ADOC.xerox.com with Internet Mail Service (5.5.2653.19)
	id <RLRRMQ7C>; Tue, 28 Aug 2001 14:51:22 -0700
Message-ID: <51B8ABCE456FD111899900805F6FD6EE067A3587@mercury.ADOC.xerox.com>
From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
To: "'Dan Wing'" <dwing@cisco.com>, Pete Resnick <presnick@Qualcomm.Com>
Cc: "'Shibata Tetsuya'" <shibata@ns1.nara.sharp.co.jp>, tony@att.com,
        receipt@cs.utk.edu, vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Tue, 28 Aug 2001 14:51:18 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


I do not believe that current level of receivers would do more than alert
the use that there has been a processing error or warning (e.g. via some
form of audio or visual alerting)  based upon the processable portion of the
MDN response. An accompanying message to the user may be more verbose and/or
friendly than the text portion of the MDN response.

One may envision future implementations where the receiver may be
preauthorized to take action based on the nature of the disposition-modifier
and the contained capabilities string.

Lloyd

> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Tuesday, August 28, 2001 1:38 PM
> To: Pete Resnick
> Cc: McIntyre, Lloyd; 'Shibata Tetsuya'; tony@att.com;
> receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> 
> 
> > >Note we need vendors to both send _and_ receive the various
> > >permutations.  If all implementations only send and do not parse
> > >or validate or do something on receipt, it doesn't pass muster
> > >for Draft Standard.
> > 
> > Eudora (certainly on the Mac and I believe also on Windows) 
> displays 
> > the disposition values to the user as text. Now, it's not doing any 
> > real parsing; it's just displaying the contents of the 
> > message/disposition-notification part as text. Shouldn't that be 
> > enough to be a "receiving" client?
> 
> Yes, good point.  We do the same, and expect the user to take some
> action based on what they see.
> 
> -d
> 


From owner-ietf-fax@mail.imc.org  Tue Aug 28 19:28:17 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23833
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 19:28:17 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SMjEe09637
	for ietf-fax-bks; Tue, 28 Aug 2001 15:45:14 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SMjCD09633
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 15:45:13 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id HAA03493;
	Wed, 29 Aug 2001 07:45:10 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id ABE46949;
	Wed, 29 Aug 2001 07:45:00 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id HAA04172; Wed, 29 Aug 2001 07:44:56 +0900
To: tony@att.com
Cc: ietf-fax@imc.org
Subject: Re: draft-ietf-fax-implementers-guide-07.txt
In-Reply-To: <3B8BDD0A.E50712@att.com>
References: <51B8ABCE456FD111899900805F6FD6EE067A3581@mercury.ADOC.xerox.com>
	<3B8BDD0A.E50712@att.com>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010829074856B.tamura@toda.ricoh.co.jp>
Date: Wed, 29 Aug 2001 07:48:56 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 13
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Tony,

> The examples in draft-ietf-fax-implementers-guide-07.txt spell the
> arguments in the MDN Disposition: headers incorrectly. In particular,
> MDN-send-automatically should be MDN-sent-automatically.

Thanks. I take care of it.

Regards,
--
Hiroshi Tamura, Ricoh Company, LTD.
E-mail: tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Tue Aug 28 19:42:19 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24002
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 19:42:18 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SN7iT09954
	for ietf-fax-bks; Tue, 28 Aug 2001 16:07:44 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SN7gD09950
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 16:07:42 -0700 (PDT)
Received: from azteca.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.74])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id HAA05516;
	Wed, 29 Aug 2001 07:59:33 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by azteca.isd.ricoh.co.jp (Mirapoint)
	with SMTP id AAZ35698;
	Wed, 29 Aug 2001 07:59:31 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id HAA04276; Wed, 29 Aug 2001 07:59:28 +0900
To: Lloyd.McIntyre@pahv.xerox.com
Cc: dwing@cisco.com, presnick@Qualcomm.Com, shibata@ns1.nara.sharp.co.jp,
        tony@att.com, receipt@cs.utk.edu, vpim@lists.neystadt.org,
        ietf-fax@imc.org
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
In-Reply-To: <51B8ABCE456FD111899900805F6FD6EE067A3587@mercury.ADOC.xerox.com>
References: <51B8ABCE456FD111899900805F6FD6EE067A3587@mercury.ADOC.xerox.com>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010829080328D.tamura@toda.ricoh.co.jp>
Date: Wed, 29 Aug 2001 08:03:28 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 63
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


As I suggested before,
my company, Ricoh,  already a IFAX ***procuct*** that deals with
"dispatched" for success and "processed/error" for failure.

I am sure most IFAX manufacutures in Japan have the similar one,
for product or prototype. They are independent, of course.

But, I do not know whether all mandatory features in RFC2298 are supported.
So, it may not be enough for Draft Standard process.

Also, I add very ***personally***,
next month, some IFAX manufacures in Japan will have interoperability tests for
only this feature in MDN. About acknowledgement of receipt or decoding of TIFF-FX.

--
Hiroshi Tamura, Ricoh Company, LTD.
E-mail: tamura@toda.ricoh.co.jp



From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Tue, 28 Aug 2001 14:51:18 -0700

> 
> I do not believe that current level of receivers would do more than alert
> the use that there has been a processing error or warning (e.g. via some
> form of audio or visual alerting)  based upon the processable portion of the
> MDN response. An accompanying message to the user may be more verbose and/or
> friendly than the text portion of the MDN response.
> 
> One may envision future implementations where the receiver may be
> preauthorized to take action based on the nature of the disposition-modifier
> and the contained capabilities string.
> 
> Lloyd
> 
> > -----Original Message-----
> > From: Dan Wing [mailto:dwing@cisco.com]
> > Sent: Tuesday, August 28, 2001 1:38 PM
> > To: Pete Resnick
> > Cc: McIntyre, Lloyd; 'Shibata Tetsuya'; tony@att.com;
> > receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> > Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> > 
> > 
> > > >Note we need vendors to both send _and_ receive the various
> > > >permutations.  If all implementations only send and do not parse
> > > >or validate or do something on receipt, it doesn't pass muster
> > > >for Draft Standard.
> > > 
> > > Eudora (certainly on the Mac and I believe also on Windows) 
> > displays 
> > > the disposition values to the user as text. Now, it's not doing any 
> > > real parsing; it's just displaying the contents of the 
> > > message/disposition-notification part as text. Shouldn't that be 
> > > enough to be a "receiving" client?
> > 
> > Yes, good point.  We do the same, and expect the user to take some
> > action based on what they see.
> > 
> > -d
> > 


From owner-ietf-fax@mail.imc.org  Tue Aug 28 19:58:06 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24137
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 19:58:05 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SNKm210283
	for ietf-fax-bks; Tue, 28 Aug 2001 16:20:48 -0700 (PDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SNKlD10279
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 16:20:47 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id f7SNIpV23521;
	Tue, 28 Aug 2001 16:18:51 -0700 (PDT)
Received: from DWINGW2K (dhcp-128-107-139-165.cisco.com [128.107.139.165])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAJ20234;
	Tue, 28 Aug 2001 16:20:35 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "Hiroshi Tamura" <tamura@toda.ricoh.co.jp>,
        <Lloyd.McIntyre@pahv.xerox.com>
Cc: <presnick@Qualcomm.Com>, <shibata@ns1.nara.sharp.co.jp>, <tony@att.com>,
        <receipt@cs.utk.edu>, <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Tue, 28 Aug 2001 16:20:34 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGOEDMEIAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Importance: Normal
In-Reply-To: <20010829080328D.tamura@toda.ricoh.co.jp>
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


What would be useful from these tests is to know which products send MDNs
other than (1) or (2), below, and the behavior of the products if they
receive (1), (2), or (3), below.

 1.  Disposition: automatic-action/MDN-sent-automatically; dispatched
 2.  Disposition: automatic-action/MDN-sent-automatically; processed/error
 3.  Disposition: automatic-action/MDN-sent-automatically; processed/xyzzy

Our implementation will transmit (1) or (2).  We will receive any form of
MDN - we actually only look for the Disposition line and send something
around up to 160 characters or the first CRLF sequence to the other fax
machine -- so we accept (1), (2), and (3), but we don't parse any of them.
(3) is as meaningful to us as (2).

As Greg mentioned, though, the MDN doesn't need to be computer parsed for it
to be useful to include in the Draft Standard.

-Dan Wing

> -----Original Message-----
> From: Hiroshi Tamura [mailto:tamura@toda.ricoh.co.jp]
> Sent: Tuesday, August 28, 2001 4:03 PM
> To: Lloyd.McIntyre@pahv.xerox.com
> Cc: dwing@cisco.com; presnick@Qualcomm.Com;
> shibata@ns1.nara.sharp.co.jp; tony@att.com; receipt@cs.utk.edu;
> vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
>
>
> As I suggested before,
> my company, Ricoh,  already a IFAX ***procuct*** that deals with
> "dispatched" for success and "processed/error" for failure.
>
> I am sure most IFAX manufacutures in Japan have the similar one,
> for product or prototype. They are independent, of course.
>
> But, I do not know whether all mandatory features in RFC2298 are supported.
> So, it may not be enough for Draft Standard process.
>
> Also, I add very ***personally***,
> next month, some IFAX manufacures in Japan will have
> interoperability tests for
> only this feature in MDN. About acknowledgement of receipt or
> decoding of TIFF-FX.
>
> --
> Hiroshi Tamura, Ricoh Company, LTD.
> E-mail: tamura@toda.ricoh.co.jp
>
>
>
> From: "McIntyre, Lloyd" <Lloyd.McIntyre@pahv.xerox.com>
> Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> Date: Tue, 28 Aug 2001 14:51:18 -0700
>
> >
> > I do not believe that current level of receivers would do more than alert
> > the use that there has been a processing error or warning (e.g. via some
> > form of audio or visual alerting)  based upon the processable
> portion of the
> > MDN response. An accompanying message to the user may be more
> verbose and/or
> > friendly than the text portion of the MDN response.
> >
> > One may envision future implementations where the receiver may be
> > preauthorized to take action based on the nature of the
> disposition-modifier
> > and the contained capabilities string.
> >
> > Lloyd
> >
> > > -----Original Message-----
> > > From: Dan Wing [mailto:dwing@cisco.com]
> > > Sent: Tuesday, August 28, 2001 1:38 PM
> > > To: Pete Resnick
> > > Cc: McIntyre, Lloyd; 'Shibata Tetsuya'; tony@att.com;
> > > receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> > > Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> > >
> > >
> > > > >Note we need vendors to both send _and_ receive the various
> > > > >permutations.  If all implementations only send and do not parse
> > > > >or validate or do something on receipt, it doesn't pass muster
> > > > >for Draft Standard.
> > > >
> > > > Eudora (certainly on the Mac and I believe also on Windows)
> > > displays
> > > > the disposition values to the user as text. Now, it's not doing any
> > > > real parsing; it's just displaying the contents of the
> > > > message/disposition-notification part as text. Shouldn't that be
> > > > enough to be a "receiving" client?
> > >
> > > Yes, good point.  We do the same, and expect the user to take some
> > > action based on what they see.
> > >
> > > -d
> > >



From owner-ietf-fax@mail.imc.org  Tue Aug 28 20:13:06 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24341
	for <fax-archive@odin.ietf.org>; Tue, 28 Aug 2001 20:13:06 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7SNYax10552
	for ietf-fax-bks; Tue, 28 Aug 2001 16:34:36 -0700 (PDT)
Received: from astro.cs.utk.edu (astro.cs.utk.edu [160.36.58.43])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7SNYZD10548
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 16:34:35 -0700 (PDT)
Received: from astro.cs.utk.edu (LOCALHOST [127.0.0.1])
        by astro.cs.utk.edu (cf 8.9.3) with ESMTP id TAA14045;
        Tue, 28 Aug 2001 19:30:37 -0400 (EDT)
Message-Id: <200108282330.TAA14045@astro.cs.utk.edu>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@cs.utk.edu>
To: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
cc: Lloyd.McIntyre@pahv.xerox.com, dwing@cisco.com, presnick@Qualcomm.Com,
        shibata@ns1.nara.sharp.co.jp, tony@att.com, receipt@cs.utk.edu,
        vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt 
In-reply-to: Your message of "Wed, 29 Aug 2001 08:03:28 +0900."
             <20010829080328D.tamura@toda.ricoh.co.jp> 
Date: Tue, 28 Aug 2001 19:30:37 -0400
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>


> But, I do not know whether all mandatory features in RFC2298 are supported.
> So, it may not be enough for Draft Standard process.

It is not necessary for any product to support all features; it is only
necessary for each feature to be supported by two products for sending
and two (perhaps different) products for receiving.

Keith


From owner-ietf-fax@mail.imc.org  Wed Aug 29 00:21:28 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28942
	for <fax-archive@odin.ietf.org>; Wed, 29 Aug 2001 00:21:27 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7T3jev15025
	for ietf-fax-bks; Tue, 28 Aug 2001 20:45:40 -0700 (PDT)
Received: from od3.sharp.co.jp (od3.sharp.co.jp [202.32.86.132])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7T3jbD15021
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 20:45:38 -0700 (PDT)
Received: by od3.sharp.co.jp; id MAA16954; Wed, 29 Aug 2001 12:45:35 +0900 (JST)
Received: from unknown(133.159.14.115) by od3.sharp.co.jp via smap (V4.2)
	id xma016925; Wed, 29 Aug 01 12:45:20 +0900
Received: from webshield-osa.sharp.co.jp (webshield-osa.sharp.co.jp [133.159.14.93])
	by od.sharp.co.jp (8.9.3/3.7W-01030618) with SMTP id MAA24202
	for <ietf-fax@imc.org>; Wed, 29 Aug 2001 12:45:19 +0900 (JST)
Received: FROM r2412027.ns1.nara.sharp.co.jp BY webshield-osa.sharp.co.jp ; Wed Aug 29 12:45:18 2001 +0900
Received: from r2412014.ns1.nara.sharp.co.jp (r2412014.ns1.nara.sharp.co.jp [10.36.18.14])
	by r2412027.ns1.nara.sharp.co.jp (8.9.3/1.00) with ESMTP id MAA08189;
	Wed, 29 Aug 2001 12:45:13 +0900
Received: by r2412014.ns1.nara.sharp.co.jp with Internet Mail Service (5.5.2650.21)
	id <RP7VLYWJ>; Wed, 29 Aug 2001 12:44:24 +0900
Message-ID: <FF52AB07D777D311AC930008C759932002F0B55D@NAR-EXCL1.ns1.nara.sharp.co.jp>
From: Shibata Tetsuya <shibata@ns1.nara.sharp.co.jp>
To: "'Tony Hansen'" <tony@att.com>
Cc: Greg Vaudreuil <gregv@lucent.com>,
        "'receipt@cs.utk.edu'"
	 <receipt@cs.utk.edu>,
        "'vpim@lists.neystadt.org'"
	 <vpim@lists.neystadt.org>,
        "'ietf-fax@imc.org'" <ietf-fax@imc.org>
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Wed, 29 Aug 2001 12:44:34 +0900
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-2022-jp"
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>



It is the prototype of Internet Fax machine.

 Regards,
 
 Tetsuya Shibata
 SHARP CORPORATION
 
 > -----Original Message-----
 > From: Tony Hansen [mailto:tony@att.com]
 > Sent: Wednesday, August 29, 2001 12:17 AM
 > To: Shibata Tetsuya
 > Cc: Greg Vaudreuil
 > Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
 > 
 > 
 > OK. What does your implementation actually implement?
 > 
 > 	Tony Hansen
 > 	tony@att.com
 > 
 > Shibata Tetsuya wrote:
 > > 
 > > I am a developer working at SHARP.
 > > 
 > >  > -----Original Message-----
 > >  > From: Tony Hansen [mailto:tony@att.com]
 > >  > Sent: Tuesday, August 28, 2001 11:24 AM
 > >  > To: McIntyre, Lloyd
 > >  > Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; 
 > ietf-fax@imc.org
 > >  > Subject: Re: [VPIM] RE: FW: I-D 
 > ACTION:draft-vaudreuil-mdnbis-00.txt
 > >  >
 > >  >
 > >  >
 > >  > Absolutely. If there ARE two (or more) implementations 
 > of anything we
 > >  > removed, we'll put them back in to the updated MDN document.
 > >  >
 > >  > So, just let us know of the implementations.
 > >  >
 > >  >      Tony Hansen
 > >  >      tony@att.com
 > >  >
 > >  > "McIntyre, Lloyd" wrote:
 > > 
 > > We have already developed the prototype which built in the 
 > "dispatched" feature.
 > > 
 > > We implemented almost the same as MGCS & TOSHIBA TEC.
 > > 
 > > "dispatched" without modifiers when succesfully decoding 
 > the received TIFF-FX file.
 > > "processed/error" in the case of the failure.
 > > 
 > > Regards,
 > > 
 > >  Tetsuya Shibata
 > >  SHARP CORPORATION
 > 


From owner-ietf-fax@mail.imc.org  Wed Aug 29 01:13:42 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00646
	for <fax-archive@odin.ietf.org>; Wed, 29 Aug 2001 01:13:41 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7T4cDO15810
	for ietf-fax-bks; Tue, 28 Aug 2001 21:38:13 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7T4cBD15806
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 21:38:11 -0700 (PDT)
Received: from delsol.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.75])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id NAA24077;
	Wed, 29 Aug 2001 13:31:02 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by delsol.isd.ricoh.co.jp (Mirapoint)
	with SMTP id ABE55262;
	Wed, 29 Aug 2001 13:30:51 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id NAA07277; Wed, 29 Aug 2001 13:30:46 +0900
To: moore@cs.utk.edu
Cc: Lloyd.McIntyre@pahv.xerox.com, dwing@cisco.com, presnick@Qualcomm.Com,
        shibata@ns1.nara.sharp.co.jp, tony@att.com, receipt@cs.utk.edu,
        vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt 
In-Reply-To: <200108282330.TAA14045@astro.cs.utk.edu>
References: <20010829080328D.tamura@toda.ricoh.co.jp>
	<200108282330.TAA14045@astro.cs.utk.edu>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010829133448D.tamura@toda.ricoh.co.jp>
Date: Wed, 29 Aug 2001 13:34:48 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 25
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Keith,

Thanks for your comment.

> > But, I do not know whether all mandatory features in RFC2298 are supported.
> > So, it may not be enough for Draft Standard process.
> 
> It is not necessary for any product to support all features; it is only
> necessary for each feature to be supported by two products for sending
> and two (perhaps different) products for receiving.

Yes, you are right. 

My above comment is not good. What I want to say is:
I do not read the I-D, so, all features the editor intends might not
be supported.

Regards,
--
Hiroshi Tamura, Ricoh Company, LTD.
E-mail: tamura@toda.ricoh.co.jp






From owner-ietf-fax@mail.imc.org  Wed Aug 29 01:31:10 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03018
	for <fax-archive@odin.ietf.org>; Wed, 29 Aug 2001 01:31:10 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7T4jIB15915
	for ietf-fax-bks; Tue, 28 Aug 2001 21:45:18 -0700 (PDT)
Received: from mail.notes.ricoh.co.jp (mail.notes.ricoh.co.jp [202.211.49.10])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7T4jGD15907
	for <ietf-fax@imc.org>; Tue, 28 Aug 2001 21:45:16 -0700 (PDT)
Received: from azteca.isd.ricoh.co.jp (IDENT:mirapoint@[133.139.250.74])
	by mail.notes.ricoh.co.jp (8.9.3+3.2W/3.7W) id NAA27268;
	Wed, 29 Aug 2001 13:38:11 +0900 (JST)
Received: from newton.toda.ricoh.co.jp (newton.toda.ricoh.co.jp [133.139.60.10])
	by azteca.isd.ricoh.co.jp (Mirapoint)
	with SMTP id AAZ43092;
	Wed, 29 Aug 2001 13:38:10 +0900 (JST)
Received: from localhost (maple.toda.ricoh.co.jp [133.139.60.73]) by newton.toda.ricoh.co.jp (8.6.11+2.4W/3.3W9-1.0S8sun) with ESMTP id NAA07354; Wed, 29 Aug 2001 13:38:05 +0900
To: dwing@cisco.com
Cc: Lloyd.McIntyre@pahv.xerox.com, presnick@Qualcomm.Com,
        shibata@ns1.nara.sharp.co.jp, tony@att.com, receipt@cs.utk.edu,
        vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
In-Reply-To: <EOEBIJPEADOODFNEJPEGOEDMEIAA.dwing@cisco.com>
References: <20010829080328D.tamura@toda.ricoh.co.jp>
	<EOEBIJPEADOODFNEJPEGOEDMEIAA.dwing@cisco.com>
X-Mailer: Mew version 1.94.2 on Emacs 20.4 / Mule 4.1 (AOI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20010829134208E.tamura@toda.ricoh.co.jp>
Date: Wed, 29 Aug 2001 13:42:08 +0900 (JST)
From: Hiroshi Tamura <tamura@toda.ricoh.co.jp>
X-Dispatcher: imput version 20000228(IM140)
Lines: 24
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


Dan,

> What would be useful from these tests is to know which products send MDNs
> other than (1) or (2), below, and the behavior of the products if they
> receive (1), (2), or (3), below.
> 
>  1.  Disposition: automatic-action/MDN-sent-automatically; dispatched
>  2.  Disposition: automatic-action/MDN-sent-automatically; processed/error
>  3.  Disposition: automatic-action/MDN-sent-automatically; processed/xyzzy
> 
> Our implementation will transmit (1) or (2).  We will receive any form of
> MDN - we actually only look for the Disposition line and send something
> around up to 160 characters or the first CRLF sequence to the other fax
> machine -- so we accept (1), (2), and (3), but we don't parse any of them.
> (3) is as meaningful to us as (2).

A Question.
Does your receiver distingush "processed/error" from "processed"?

Regards,
--
Hiroshi Tamura, Ricoh Company, LTD.
E-mail: tamura@toda.ricoh.co.jp



From owner-ietf-fax@mail.imc.org  Wed Aug 29 10:13:46 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28267
	for <fax-archive@odin.ietf.org>; Wed, 29 Aug 2001 10:13:45 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7TDYbo28687
	for ietf-fax-bks; Wed, 29 Aug 2001 06:34:37 -0700 (PDT)
Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7TDYZD28679
	for <ietf-fax@imc.org>; Wed, 29 Aug 2001 06:34:35 -0700 (PDT)
Received: from dns.maillennium.att.com ([135.25.114.99])
	by ckmso1.proxy.att.com (AT&T IPNS/MSO-3.0) with ESMTP id f7TDYQO19380
	for <ietf-fax@imc.org>; Wed, 29 Aug 2001 09:34:26 -0400 (EDT)
Received: from att.com ([135.210.75.40])
          by maillennium.att.com (labmail) with SMTP
          id <2001082913342009900rl9ime>
          (Authid: tony@maillennium.att.com);
          Wed, 29 Aug 2001 13:34:21 +0000
Message-ID: <3B8CEEF6.74062DA8@att.com>
Date: Wed, 29 Aug 2001 09:32:38 -0400
From: Tony Hansen <tony@att.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: receipt@cs.utk.edu, vpim@lists.neystadt.org, ietf-fax@imc.org
Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
References: <20010829080328D.tamura@toda.ricoh.co.jp>
		<EOEBIJPEADOODFNEJPEGOEDMEIAA.dwing@cisco.com> <20010829134208E.tamura@toda.ricoh.co.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


The internet fax implementer's guide
(draft-ietf-fax-implementers-guide-07.txt) also specifies the use of
processed/warning, as in:

Disposition: automatic-action/MDN-sent-automatically; processed/warning

Does anyone implement that?

	Tony

Hiroshi Tamura wrote:
> 
> Dan,
> 
> > What would be useful from these tests is to know which products send MDNs
> > other than (1) or (2), below, and the behavior of the products if they
> > receive (1), (2), or (3), below.
> >
> >  1.  Disposition: automatic-action/MDN-sent-automatically; dispatched
> >  2.  Disposition: automatic-action/MDN-sent-automatically; processed/error
> >  3.  Disposition: automatic-action/MDN-sent-automatically; processed/xyzzy
> >
> > Our implementation will transmit (1) or (2).  We will receive any form of
> > MDN - we actually only look for the Disposition line and send something
> > around up to 160 characters or the first CRLF sequence to the other fax
> > machine -- so we accept (1), (2), and (3), but we don't parse any of them.
> > (3) is as meaningful to us as (2).
> 
> A Question.
> Does your receiver distingush "processed/error" from "processed"?
> 
> Regards,
> --
> Hiroshi Tamura, Ricoh Company, LTD.
> E-mail: tamura@toda.ricoh.co.jp


From owner-ietf-fax@mail.imc.org  Wed Aug 29 13:19:17 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03570
	for <fax-archive@odin.ietf.org>; Wed, 29 Aug 2001 13:19:17 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7TGekq07280
	for ietf-fax-bks; Wed, 29 Aug 2001 09:40:46 -0700 (PDT)
Received: from sj-msg-core-4.cisco.com (sj-msg-core-4.cisco.com [171.71.163.10])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7TGejD07276
	for <ietf-fax@imc.org>; Wed, 29 Aug 2001 09:40:45 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-4.cisco.com (8.11.3/8.9.1) with ESMTP id f7TGeqN16606;
	Wed, 29 Aug 2001 09:40:52 -0700 (PDT)
Received: from DWINGW2K (dwings-dsl5.cisco.com [10.19.89.166])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAJ33954;
	Wed, 29 Aug 2001 09:40:39 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "Hiroshi Tamura" <tamura@toda.ricoh.co.jp>
Cc: <Lloyd.McIntyre@pahv.xerox.com>, <presnick@Qualcomm.Com>,
        <shibata@ns1.nara.sharp.co.jp>, <tony@att.com>, <receipt@cs.utk.edu>,
        <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Wed, 29 Aug 2001 09:40:38 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGEEGGEIAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <20010829134208E.tamura@toda.ricoh.co.jp>
Importance: Normal
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


> > What would be useful from these tests is to know which products send MDNs
> > other than (1) or (2), below, and the behavior of the products if they
> > receive (1), (2), or (3), below.
> >
> >  1.  Disposition: automatic-action/MDN-sent-automatically; dispatched
> >  2.  Disposition: automatic-action/MDN-sent-automatically;
> processed/error
> >  3.  Disposition: automatic-action/MDN-sent-automatically;
> processed/xyzzy
> >
> > Our implementation will transmit (1) or (2).  We will receive any form of
> > MDN - we actually only look for the Disposition line and send something
> > around up to 160 characters or the first CRLF sequence to the other fax
> > machine -- so we accept (1), (2), and (3), but we don't parse
> any of them.
> > (3) is as meaningful to us as (2).
>
> A Question.
> Does your receiver distingush "processed/error" from "processed"?

No - the text is sent, as-is, to the remote PSTN fax machine.  It will also
send "DanWingHasAMustache" if that is on the Disposition: line.  It doesn't
examine the contents of the text at all.

-d



From owner-ietf-fax@mail.imc.org  Wed Aug 29 13:21:01 2001
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03617
	for <fax-archive@odin.ietf.org>; Wed, 29 Aug 2001 13:21:01 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]])
	by above.proper.com (8.11.6/8.11.3) id f7TGkBb07414
	for ietf-fax-bks; Wed, 29 Aug 2001 09:46:11 -0700 (PDT)
Received: from sj-msg-core-3.cisco.com (sj-msg-core-3.cisco.com [171.70.157.152])
	by above.proper.com (8.11.6/8.11.3) with ESMTP id f7TGkBD07410
	for <ietf-fax@imc.org>; Wed, 29 Aug 2001 09:46:11 -0700 (PDT)
Received: from mira-sjcm-3.cisco.com (mira-sjcm-3.cisco.com [171.69.24.15])
	by sj-msg-core-3.cisco.com (8.11.3/8.9.1) with ESMTP id f7TGiCV24727;
	Wed, 29 Aug 2001 09:44:12 -0700 (PDT)
Received: from DWINGW2K (dwings-dsl5.cisco.com [10.19.89.166])
	by mira-sjcm-3.cisco.com (Mirapoint)
	with SMTP id AAJ34101;
	Wed, 29 Aug 2001 09:46:04 -0700 (PDT)
From: "Dan Wing" <dwing@cisco.com>
To: "Tony Hansen" <tony@att.com>, <receipt@cs.utk.edu>,
        <vpim@lists.neystadt.org>, <ietf-fax@imc.org>
Subject: RE: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Date: Wed, 29 Aug 2001 09:46:03 -0700
Message-ID: <EOEBIJPEADOODFNEJPEGIEGIEIAA.dwing@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <3B8CEEF6.74062DA8@att.com>
Importance: Normal
Sender: owner-ietf-fax@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-fax/mail-archive/>
List-ID: <ietf-fax.imc.org>
List-Unsubscribe: <mailto:ietf-fax-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit


No, we don't.

In our TIFF decoder, we do track situations where pointers were invalid
or offsets were wrong, and those are counted.  However, the mail application
doesn't look at that warning counter when generating the MDN; we're only
looking at the error boolean when generating the MDN.

So we could add this pretty easily, but at the time we coded this we
felt that "processed/warning" could be misinterpreted.  After all, the
user can't do anything to fix their implementation to avoid the warning.
All that "processed/warning" really tells you is "I received something
that I found difficult to parse, and there may be some side-effects
because of that difficulty."

I wouldn't complain if it were dropped from the MDNbis.

-d

> -----Original Message-----
> From: owner-ietf-fax@mail.imc.org [mailto:owner-ietf-fax@mail.imc.org]On
> Behalf Of Tony Hansen
> Sent: Wednesday, August 29, 2001 6:33 AM
> To: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
>
>
>
> The internet fax implementer's guide
> (draft-ietf-fax-implementers-guide-07.txt) also specifies the use of
> processed/warning, as in:
>
> Disposition: automatic-action/MDN-sent-automatically; processed/warning
>
> Does anyone implement that?
>
> 	Tony
>
> Hiroshi Tamura wrote:
> >
> > Dan,
> >
> > > What would be useful from these tests is to know which
> products send MDNs
> > > other than (1) or (2), below, and the behavior of the products if they
> > > receive (1), (2), or (3), below.
> > >
> > >  1.  Disposition: automatic-action/MDN-sent-automatically; dispatched
> > >  2.  Disposition: automatic-action/MDN-sent-automatically;
> processed/error
> > >  3.  Disposition: automatic-action/MDN-sent-automatically;
> processed/xyzzy
> > >
> > > Our implementation will transmit (1) or (2).  We will receive
> any form of
> > > MDN - we actually only look for the Disposition line and send something
> > > around up to 160 characters or the first CRLF sequence to the other fax
> > > machine -- so we accept (1), (2), and (3), but we don't parse
> any of them.
> > > (3) is as meaningful to us as (2).
> >
> > A Question.
> > Does your receiver distingush "processed/error" from "processed"?
> >
> > Regards,
> > --
> > Hiroshi Tamura, Ricoh Company, LTD.
> > E-mail: tamura@toda.ricoh.co.jp



