[idn] BCP for IDN..

["Soobok Lee" <lsb@postel.co.kr>]

IMO,  BCP for IDN is the right place to put  these things:

   :   unassigned code points ( also in nameprep already)
   :   defective combining sequences
          -  umcombined diacritical mark and signs ( <acute>.com)
          -  invalid hangul jamo sequences   
   :   defective-rendering-engine-oriented  "equivalence"
         -  <acute><acute> vs <acute>
   :   similarly-looking characters that can be used for spoofing
         -  <latin 8> and  <bengali 4>
         -  <latin B> and  <cyrillic b>
         -  katakana ka and chinses 'power' letter
   :   special characters (mathematical,dingbets,music signs ...)
   :   other equivalences  relevant to  IPR issues
  
If  and only if TC/SC/Kanji/Hanja equivalences  can't be in nameprep,
  it may be put into here.

May BCP(as informational RFC) be revised and evolved 
even after it is finalized with the minimal set of guidelines for 
idn identifier security ?  
 
I have found some BCPs in the IETF homepage.

  3. http URL:draft-bouwen-megaco-isdn-bcp-01.txt
    Summary
    Title: Best Current Practice for Megaco-Sigtran Interaction in ISDN Acces...

  9. http URL:draft-nickless-ipv4-mcast-bcp-01.txt
    Summary
    Title: IPv4 Multicast Best Current Practice

I am not  a fulltime IETF participants like most of you.
I think  several co-authors with diverse expertise 
should work together to finish this BCP in timely manner.

Soobok


----- Original Message ----- 
From: "Mike Astle" <astle@new.net>
Cc: <idn@ops.ietf.org>
Sent: Friday, August 31, 2001 1:38 AM
Subject: Re: [idn] spoofing by combining diacritical marks


> Is anyone working on such a document?
> 
> On Thu, 30 Aug 2001, James Seng/Personal wrote:
> 
> > What you are looking for is a Best Current Practice draft for operation
> > of IDN. Currently there is none so my best suggestion is to write a new
> > I-D on this.
> 
>