Internet Fax (fax)

Graham Klyne | 1 Sep 1997 15:56

Picon

ADDRESSING: Do not recommend "quoted-string"

The following was posted to the DRUMS mailing list.  It may have some
impact on our deliberations regarding the form of a fax address.

GK.
---

>X-Sender: jpalme <at> dsv.su.se (Unverified)
>Date: Sun, 31 Aug 1997 10:44:02 +0200
>To: drums <at> cs.utk.edu
>From: Jacob Palme <jpalme <at> dsv.su.se>
>Subject: Do not recommend "quoted-string"
>
>Proposed addition to draft-ietf-drums-msg-fmt-02.txt:
>
>The use of "quoted-string" is known to cause problems for some mailers,
>therefore mailers SHOULD not use quoted-strings in addr-specs over which
>they have control, but MUST of course accept quoted-string in all other
>addr-specs.
>
>------------------------------------------------------------------------
>Jacob Palme <jpalme <at> dsv.su.se> (Stockholm University and KTH)
>for more info see URL: http://www.dsv.su.se/~jpalme

------------
Graham Klyne
GK <at> ACM.ORG

Graham Klyne | 1 Sep 1997 15:56

RE: E.164 subaddressing

At 11:03 AM 8/29/97 -0400, Vance Shipley wrote:
>Richard Shockey writes:
>}  In all honesty and sincerity I have never heard of E.164... what is it and
>}  what is it actually used for, if anything?
>
>
>My apologies.  Let me explain.
>
[...]

Thank you for that background information.  I would like to put a
supplementary question (possibly dumb)...

Did Group 4 fax go any way to reconciling the difference/distinction
between "E.164 sub-addresses" (note quotes  and "T.33 sub-addresses"?

GK.
---

Graham Klyne | 1 Sep 1997 18:20

Picon

FW: Refining the scope of PINT's work

For information:

Some time ago there was a discussion in this list of how offramp billing
for Internet fax might work.

More recently there has been discussion of the need for a receiving fax
machine to send a confirmation (rather than hop-by-hop confirmation) which
may also raise the issue of who pays for any call needed to send a
confirmation message.

I have just noted that work of the recently-formed PINT WG may have a
bearing on this -- I excerpt a section of the message which carries this
implication.  I have left a fair amount of other detail from the message in
order to give some context.

GK.
---

>From: "Scott Petrack"<Scott_Petrack <at> vocaltec.com>
>To: pint <at> lists.research.bell-labs.com
>Date: Mon, 1 Sep 1997 16:53:36 +0200
>Subject: Refining the scope of PINT's work
>Sender: owner-pint <at> lists.research.bell-labs.com

[...]

>B. There seemed to be agreement that we had to give very precise
>definitions of the "example services" that are referred to in the charter.
>Here is a quick attempt at such definitions. I spend the longest time on
>the first service, and most of the fuzzy issues are addressed there. After

(Continue reading)

Graham Klyne | 1 Sep 1997 22:27

Picon

draft-wing-smtp-session-00.txt

Dan,

I think I'm down to real nit-picking on this draft now, so a few trivial
points for you to consider...

1.  Abstract

This memo defines an extension to SMTP [RFC821] which provides a
mechanism for immediate message delivery over ESMTP, bypassing SMTP's
normal store-and-forward behavior.

>>>
I note that you are also citing a document from the new DRUMS
(work-in-progress) series: would it be appropriate to be consistently cite
the DRUMs work OR the original RFC 821/822 documents?
<<<

2.  Introduction

Historically, SMTP [RFC821, RFC822] and [SMTP-EXT] have been used for
store and forward delivery of messages.  This draft defines a new
transport mode for ESMTP delivery known as SESSION.  When SESSION is
used, the ESMTP server delivers the message before the ESMTP client
disconnects from it.

>>>
I note that you cite [RFC822], but as far as I can tell your draft stands
independently of the format of the messages that are transferred.
<<<

(Continue reading)

Graham Klyne | 2 Sep 1997 07:16

Picon

Re: What's PINT

At 12:50 PM 9/1/97 -0500, Richard Shockey wrote:
>At 05:20 PM 9/1/97 +0100, you wrote:
>>For information:
>
>What is this group and what is the scope of its work?

I was afraid someone might ask me that 

I'm not very clear, but it's something to do with the use of Internet
(type) networks to manipulate PSTN (circuit-switch style) network systems.
The WG itself seems to be in the process of defining exactly what issues it
is trying to address.

One of the terms they use, which I do not fully understand, is 'Intelligent
Network'.  This seems to be a reference to a new generation of
circuit-switch network which can behave in ways that are more complex than
a traditional circuit-switch (telephone) network.  I think they are looking
to define an Internet-carried protocol which can be used to coordinate the
actions of this 'Intelligent Network'.

I signed up to this working group as a 'lurker' sometime after I started
tracking the IETF FAX discussion list, as I figured that any group who were
looking at interactions between PSTN and the Internet might have some kind
of bearing on what Internet fax is trying to do.  I must confess to not
having a great understanding of that which they discuss.

GK.
---

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

(Continue reading)

Graham Klyne | 2 Sep 1997 07:16

Picon

draft-wing-smtp-capabilities-00.txt

Dan,

A few (mostly trivial) comments on your ESMTP capabilities identification
draft..

GK.
---

1.  Abstract

This document describes an extension to SMTP [RFC821] which provides a
mechanism for capabilities exchange so the sender knows the capabilities
of the ultimate recipient or the ESMTP server itself.

>>>
How about: "This document describes an extension to SMTP [RFC821] which
provides a mechanism for capabilities exchange so the sender of a message
can know selected capabilities of its ultimate recipient, or of the message
transmission path to that recipient" ?
<<<

2.  Introduction

This memo defines a mechanism to allow an ESMTP client to determine the
capabilities (such as viewers, word processors, and color support) and
preferences (such language) of a recipient, which allows the ESMTP
client to send a message in a format that is usable by the recipient.

>>>
"such language" -> "such as language" ?

(Continue reading)

Claudio Allocchio +39 40 3758523 | 3 Sep 1997 00:45

Picon

Re: ADDRESSING: Do not recommend "quoted-string"

On Mon, 1 Sep 1997 GK <at> ACM.ORG wrote:

> 
> >X-Sender: jpalme <at> dsv.su.se (Unverified)
> >Date: Sun, 31 Aug 1997 10:44:02 +0200
> >To: drums <at> cs.utk.edu
> >From: Jacob Palme <jpalme <at> dsv.su.se>
> >Subject: Do not recommend "quoted-string"
> >

Yes, it is one of the proposed additions, which however is still under 
strong discussion, as there are cases where you can ONLY generate quotes 
string. The reccomendation tries to minimize problems, not to forbid the 
use of "quoted-string". Examples:

   /c=gb/a=concert/p=Morrison Ltd./s=Sales/

if there is NOT a published MIXER mapping rule can only be converted into

   "/c=gb/a=concert/p=Morrison Ltd./s=Sales/" <at> somegateway

Jacob's proposal, thus, suggest "get a valid published MIXER mapping 
rule", but of not... no way.

> >Proposed addition to draft-ietf-drums-msg-fmt-02.txt:
> >
> >The use of "quoted-string" is known to cause problems for some mailers,
> >therefore mailers SHOULD not use quoted-strings in addr-specs over which
> >they have control, but MUST of course accept quoted-string in all other

(Continue reading)

Claudio Allocchio +39 40 3758523 | 3 Sep 1997 02:21

Picon

draft-ietf-fax-addressing-00.txt


Hallo,the complete ABNF definition for addresing is coming in the next 
message. 

In some points you will find sections marked with > in the first column.
Read them carefully as the include optional or choices to be defined by
the group. 

The definition is detailed, as it allows a number of possible extensions 
and defines a syntax for them. However it can scale down to minimal 
specification like:

                        /DD.fax=+3940226338 <at> faxgw

The reason for the "/DD." prefix is explained into the document, and it 
is needed to avoid absurd results in case a MIXER gateway is crossed.

Could we please try to focus on the > points to find answers for them?

More over, please note the document deals with address syntax, not with
semantics.

regards
Claudio
-------------------------------------------------------------------------------
Claudio Allocchio                          Claudio.Allocchio <at> elettra.trieste.it

tel: +39 40 3758523                        G=Claudio; S=Allocchio; O=elettra;
fax: +39 40 3758565                        P=Trieste; A=garr; C=it;

(Continue reading)

Claudio Allocchio +39 40 3758523 | 3 Sep 1997 02:22

Picon

draft-ietf-fax-addressing-00.txt


Network Working                                           C. Allocchio
Group                                                       GARR-Italy
INTERNET-DRAFT                                          September 1997
                                               Expires:     March 1998
                                File: draft-ietf-fax-addressing-00.txt

 
             Fax address format in e-mail services

Status of this Memo

This document is an Internet Draft.  Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas,
and its Working Groups.  Note that other groups may also distribute
working documents as Internet Drafts.  Internet Drafts are draft
documents valid for a maximum of six months.  Internet Drafts may be
updated, replaced, or obsoleted by other documents at any time.  It is
not appropriate to use Internet Drafts as reference material or to
cite them other than as a ``working draft'' or ``work in progress.''
Please check the I-D abstract listing contained in each Internet Draft
directory to learn the current status of this or any other Internet
Draft.

1. Introduction

   Since the very first e-mail to fax gateway objects appeared, a 
   number of different methods to specify a fax address into an
   e-mail address have been used by implementors. Two major objectives
   for this were

(Continue reading)

Claudio Allocchio +39 40 3758523 | 3 Sep 1997 08:21

Picon

multiple copies of draft-ietf-fax-addressing-00.txt


Hallo,
sorry to all of you who received multiple copies of the draft: actually 
only one copy was posted, but apparently it was sent out more than once 
from imc.irg mailer. My logs just state one copy sent successfully.

Sorry again.
Claudio

-------------------------------------------------------------------------------
Claudio Allocchio                          Claudio.Allocchio <at> elettra.trieste.it

tel: +39 40 3758523                        G=Claudio; S=Allocchio; O=elettra;
fax: +39 40 3758565                        P=Trieste; A=garr; C=it;

---------- Forwarded message ----------
Date: Tue, 02 SEP 97 13:30:17 +0000
From: hsilbiger <at> exit109.com
To: Claudio.Allocchio <at> elettra.trieste.it
Subject: RE: draft-ietf-fax-addressing-00.txt

I received three identical copies of this document.
----------
From: 	Claudio Allocchio +39 40 3758523[SMTP:Claudio.Allocchio <at> elettra.trieste.it]
Sent: 	Tuesday, September 02, 1997 8:22 PM
To: 	ietf-fax <at> imc.org
Subject: 	draft-ietf-fax-addressing-00.txt

Group

gmane.ietf.fax.

Search Archive

Page

1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 27

Articles in period: 261

September 1997

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane

Recent entries

Status (1 Apr 2006)
the file (18 Jan 2006)
Hello (17 Jan 2006)
Fw: Real show (17 Jan 2006)
Fwd: Crazy illegal Sex! (17 Jan 2006)
All documents are published! (21 Nov 2005)
RFC 4143 on Facsimile Using Internet Mail (IFAX) Service of ENUM (19 Nov 2005)
RFC 4141 on SMTP and MIME Extensions for Content Conversion (19 Nov 2005)
RFC 4142 on Full-mode Fax Profile for Internet Mail (FFPIM) (19 Nov 2005)
RFC 4161 on Guidelines for Optional Services for Internet Fax Gateways (1 Sep 2005)
RFC 4160 on Internet Fax Gateway Requirements (1 Sep 2005)
(13 Jul 2005)
test (9 May 2005)
IETF FAX Bye Bye Dinner - Tuesday March 8th, 7.30PM (6 Mar 2005)
bye, Internet Fax ! (28 Feb 2005)
WG Action: Conclusion of Internet Fax (fax) (24 Feb 2005)
WG Action: Conclusion of Internet Fax (fax) (24 Feb 2005)
I-D ACTION:draft-ietf-fax-gateway-protocol-13.txt (23 Feb 2005)
Internet FAX WG - we are FINALLY done! (22 Feb 2005)
Document Action: 'Guideline of optional services for Internet (22 Feb 2005)
Document Action: 'Internet FAX Gateway Functions' to Informat (22 Feb 2005)

Archives

1	April 2006
4	January 2006
7	November 2005
2	September 2005
1	July 2005
1	May 2005
1	March 2005
15	February 2005
5	January 2005
6	December 2004
4	August 2004
35	July 2004
13	June 2004
2	May 2004
1	April 2004
7	March 2004
5	February 2004
2	December 2003
2	November 2003
1	September 2003
6	August 2003
16	July 2003
11	June 2003
11	May 2003
12	April 2003
9	March 2003
25	February 2003
3	January 2003
38	December 2002
28	November 2002
23	October 2002
25	September 2002
18	August 2002
214	July 2002
22	June 2002
3	May 2002
17	April 2002
53	March 2002
14	February 2002
26	January 2002
47	December 2001
28	November 2001
19	October 2001
21	September 2001
76	August 2001
61	July 2001
48	June 2001
26	May 2001
11	April 2001
152	March 2001
95	February 2001
16	January 2001
18	December 2000
44	November 2000
34	October 2000
18	September 2000
26	August 2000
58	July 2000
20	June 2000
34	May 2000
34	April 2000
61	March 2000
23	February 2000
35	January 2000
11	December 1999
12	November 1999
51	October 1999
28	September 1999
24	August 1999
22	July 1999
62	June 1999
14	May 1999
29	April 1999
64	March 1999
71	February 1999
34	January 1999
33	December 1998
64	November 1998
132	October 1998
115	September 1998
103	August 1998
289	July 1998
257	June 1998
176	May 1998
24	April 1998
104	March 1998
40	February 1998
164	January 1998
369	December 1997
248	November 1997
97	October 1997
260	September 1997
106	August 1997
116	July 1997
94	June 1997
359	May 1997
165	April 1997
61	March 1997
33	February 1997
244	January 1997
267	December 1996
159	November 1996
37	October 1996
96	September 1996
35	August 1996
6	July 1996

Design

Zawodny | Right Menu | Left Menu

Your Own Design

Paste the URL of your CSS below. Download CSS template