Subaddress Revisited

[Ken Camarro <kcamarro@xxxxxxxx>]

Thanks for your excellent posting.

Once again *it's only software* and a discretionary issue in the server
programming.

I think that what you are saying is that there is no reason why we cannot
implement subaddressing in the efax address.

A recipient will not publish a fax subaddress address unless the internet
interconnect system (the server or whatever) is compliant and can support
the subaddress application.  This is the recipient's responsibility.
Otherwise separate calls must be made for subscriber 1 and 2 etc.
 
Public and private servers have to be upgraded to accommodate subaddress.

thus efax = kcamarro#123#321@snet.net

This signifies a distribution of the message to Ken and Tom.

where 123 is Ken and 321 is Tom.

Ken sends and receives under 123 and Tom sends and receives under 321.

It won't work if there is no subaddress support at the interconnect.

Note:  <kcamarro#123#ABC@snet.net> would be illegal following ITU
Subaddress since Fax Subaddress is only numeric. #123#12$#125 etc.

However, efax could be designed to support #ABC or #123 or 1B2.  The
problem here is that this would pose a problem for the legacy fax device
which does not have an alphanumeric keyboard.  However the legacy device
will go through Gateway which has to support alphanumeric by default so
legacy fax system will be able to access an alphanumeric efax subaddress.   

The efax device can therefore use alphanumeric efax subaddresses when
within the efax realm that is efax to efax.  The efax will be able to send
to a legacy fax device using legacy fax subaddress through a Gateway.  And
of course, the efax san default to PSTN and use the legacy fax subaddress.

The efax device will have an alphanumeric keyboard or data entry mechanism.

PROPOSAL: EFAX SUBADDRESSES TO BE ALPHANUMERIC

I therefore propose that efax subaddresses be alphanumeric.

PLACE FOR TOKENS NOTA BENE (NB)

You said:

>Now let's take this and consider what it means in light of your stated
application. Your requirement here basically boils down to having agents that
can select a mailbox based on only part of the local part of an address. In
addition, the subaddress information has to be made available as part of
message; it cannot simply be lost  at the time of delivery. (There's a
place to
put this information, but a given agent may or may not actually put it in.)

This seems to be very important to lots of things concerning ietf-fax such
as its a JPEG message etc.  

Best regards,

Ken Camarro
Camarro Research
Marketing and Product Development

580 Commerce Drive
Fairfield, CT 06432-5513

Tel: 203-336-4566
Fax: 203-331-0470
Email: kcamarro@snet.net
Efax: To Be

Information on 500 Page Office MFP Twelve Focus Group Project Report:

   <http://www.mfpa.org/cgi-bin/HyperNews/get.cgi/industry-pr/2.html>