Bob,

I have not yet taken up this item, but I certainly do not expect to put an H.323 URL into the email-ID alias field. Is that what the text said?

The URL should only be used in the url-ID field. If I understand what you're saying, I completely agree with you.

Paul

----- 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 Sent: Wednesday, June 14, 2000 9:53 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