Re: Question on ECML address country code usage

[Donald Eastlake 3rd <dee3@torque.pothole.com>]

(1) ECML is supposed to support a variety of existing financial
protocols used on existing networks. As far as I know, all of them that
need any jurisdictional information include the country code (commonly
in the form on the UN country number which is equivalent). This alone is
sufficient justification for including ISO country code, keeping in mind
that all fields in ECML are optional and can be used or not as the
participants choose.

(2) ISO 3166 is a well defined standard which anyone can consult and
will therefore interpert the same way. I.E., it is interoperable, the
major goal of IETF protocols. Poking holes in it without specifying an
interoperable replacement seems pretty insignificant to me. This reason
alone is sufficient justification to include ISO country code as an
optional jurisdiction related field.

Donald

PS: I'm about to leave for vacation returning 1 Sept. so will probably 
not be very responsive between now and then.

On Thu, 22 Aug 2002, Eric Brunner-Williams in Portland Maine wrote:

> Date: Thu, 22 Aug 2002 13:52:38 -0400
> From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
> To: Eastlake III Donald-LDE008 <Donald.Eastlake@motorola.com>
> Cc: ietf-trade@lists.elistx.com, brunner@nic-naa.net
> Subject: Re: Question on ECML address country code usage
> 
> Donald,
> 
> You and I (and Bill) wrote the IANA considerations for the DNS, and inspite
> of your initial attachment to iso3166, there was no technical necessity in
> that BCP to cite iso3166.
> 
> What is the compelling necessity here?
> 
> Eric
> 

-- 
======================================================================
 Donald E. Eastlake 3rd                       dee3@torque.pothole.com
 155 Beaver Street              +1-508-634-2066(h) +1-508-851-8280(w)
 Milford, MA 01757 USA                   Donald.Eastlake@motorola.com