Isaac@gui.consumers.com (08/17/90)
We are now beginning to understand the issues involved in attaching a PRMD to multiple ADMDs within a country. Draft British Standard Specification for Electronic Messaging Implementing ISO/IEC 10021 in the United Kingdom describes the UK approach to these problems. Has anyone have any thought on what should happens when a PRMD in a country without any ADMDs wishes to use the services of an ADMDs in a different countries. Does it means that they will have to use a foreign country code for themselves? What happens when this PRMD wants to use the services of different ADMDs in different countries at different times? Do they need to use different country codes and therefore have different ORaddresses depending on which ADMD they use for the message? Or is this allowed at all? Isaac Chan, Consumers Software Inc. isaac@gui.consumers.com
rwj@arch2.att.com (08/17/90)
Hi Folks, In line with Isaac's question, see attached, what are the addressing consequences or issues for a PRMD user associated with an ADMD that spans international boundaries? In other words, a PRMD connected to a supra-ADMD? Should we seek to recognize a reserved Country Code like PrintableString "XX" and NumbericString "000" and seek to set up an international registry for those ADMDs wishing to operate as a supra-ADMD. Would an ADMD serving PRMDs in other countries, but not offering subscriber services to residents in that country, as suggested in Isaac's message, be considered a supra-ADMD? What are the international law, billing, currency and settlement issues surrounding such a venture? Should this discussion and ultimate solution, if there is one that can be agreed, find its way into the CCITT/ISO standards arena as a US contribution? Should the ITU be approached to set up such a service? How much unlike is this from the interworking and addressing issues created by a supra-PRMDs? Dick J. AT&T Bell Labs ===================================================== >>We are now beginning to understand the issues involved in attaching a PRMD >>to multiple ADMDs within a country. >> >>Draft British Standard Specification for Electronic Messaging Implementing >>ISO/IEC 10021 in the United Kingdom describes the UK approach to these >>problems. >> >>Has anyone have any thought on what should happens when a PRMD in a country >>without any ADMDs wishes to use the services of an ADMDs in a different >>countries. Does it means that they will have to use a foreign country code >>for themselves? What happens when this PRMD wants to use the services of >>different ADMDs in different countries at different times? Do they need >>to use different country codes and therefore have different ORaddresses >>depending on which ADMD they use for the message? Or is this allowed at all? >> >> >>Isaac Chan, Consumers Software Inc. >>isaac@gui.consumers.com
eskovgaa@UVCW.UVIC.CA (Erik Skovgaard) (08/18/90)
Re. the multi-national ADMD
In my opinion, such an ADMD should choose which country it belongs in
or else register its name in multiple countries. In the latter case
it would then be considered multiple separate MTAs for routing
purposes.
Why make routing more complicated? Most of the cases, that have been
presented as possible routing problems, would only be encountered
very rarely, so why not simply disallow these extreme cases.
To get on my soapbox: standards should help interoperability, not
needlessly complicate it.
....Erik.daniel@retix.retix.COM (Daniel Chu) (08/24/90)
I agree with Erik that ADMD in multiple nations should be treated as different entity. Some profile group will have to come up with an agreement that every one will follow. Separate MTA make it easier to route base on country code. This is only my personal opionion and has nothing to do with my company's.