Bob! On theoretical basis, I COMPLETELY agree with your statement.
From practical point of view (how many, and what type of aliases, the end
user has the access to) we may need more work in Portland. Orit Levin RADVision Inc. 575 Corporate Drive Suite 420 Mahwah, NJ 07430 Tel: 1 201 529 4300 (230) Fax: 1 201 529 3516 www.radvision.com orit@radvision.com -----Original Message----- From: Callaghan, Robert Robert.Callaghan@icn.siemens.com To: 'Orit Levin' orit@radvision.com; 'Paul E. Jones' paulej@PACKETIZER.COM Cc: Mailing list for parties associated with ITU-T Study Group 16 (E-mail) ITU-SG16@mailbag.cps.intel.com Date: Wednesday, June 14, 2000 3:51 PM Subject: RE: H.323 URL
Orit,
In my opinion, an email-ID alias conforms to RFC-822 and is interpreted according the rules stated in H.225.0. An H.323-URL-ID conforms to TD-40a/Osaka and is interpreted according to the rules stated in TD-40a.
An
H.323-ID is a character string without any rules of interpretation. I see no need to blend these contexts. All three addressing modes can be use; each in its own context.
However, these are my opinion. Maybe more work is needed in Portland.
Bob
Robert Callaghan Siemens Enterprise Networks Tel: +1.561.923.1756 Fax: +1.561.923.1403 Email: Robert.Callaghan@ICN.Siemens.com
-----Original Message----- From: Orit Levin [mailto:orit@radvision.com] Sent: Wednesday, June 14, 2000 11:45 AM To: Callaghan, Robert; 'Paul E. Jones' Cc: Mailing list for parties associated with ITU-T Study Group 16 (E-mail) Subject: Re: H.323 URL
Hello Bob and Paul! I don't see backwards compatibility problem, when the URL says explicitly H323-URL. An appropriate change may be to state, that the default meaning
of
url, encoded into email-ID alias, is according to RFC-822. Now, I feel a need to put a chapter explaining what is the meaning of email URL (apart from its syntax) when used in H.323 Network. There is some explanation in H.225.0 Appendix IV. Do you find it clear and sufficient? Orit Levin RADVision Inc. 575 Corporate Drive Suite 420 Mahwah, NJ 07430 Tel: 1 201 529 4300 (230) Fax: 1 201 529 3516 www.radvision.com orit@radvision.com -----Original Message----- From: Callaghan, Robert Robert.Callaghan@icn.siemens.com To: 'Paul E. Jones' paulej@PACKETIZER.COM; 'Orit Levin' orit@radvision.com Cc: Mailing list for parties associated with ITU-T Study Group 16 (E-mail) ITU-SG16@mailbag.cps.intel.com Date: Wednesday, June 14, 2000 9:56 AM Subject: H.323 URL
Paul,
I have a backward compatibility item for you to think about.
TD-40/Osaka states that the H323-URL may be coded into the email-ID for alias address. However, H.225.0 states that the email-ID shall conform to RFC822. This is an exclusionary requirement in that other standards may
not
be used. Also, Note 4 of the BNF definition of the H323-URL clearly
states
that that the H323-URL is *not* compatible with RFC822.
Therefor, I propose that the H323-URL cannot be coded into the email-ID
for
alias address because of compatibility problems.
Bob
Robert Callaghan Siemens Enterprise Networks Tel: +1.561.923.1756 Fax: +1.561.923.1403 Email: Robert.Callaghan@ICN.Siemens.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com