
From jefsey@jefsey.com  Mon Apr  5 16:24:52 2010
Return-Path: <jefsey@jefsey.com>
X-Original-To: iucg@core3.amsl.com
Delivered-To: iucg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 820E93A67B1 for <iucg@core3.amsl.com>; Mon,  5 Apr 2010 16:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.22
X-Spam-Level: *
X-Spam-Status: No, score=1.22 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DATE_IN_PAST_24_48=1.219]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hWzMLRZPqIeW for <iucg@core3.amsl.com>; Mon,  5 Apr 2010 16:24:51 -0700 (PDT)
Received: from montage2.altserver.com (montage2.altserver.com [72.34.52.22]) by core3.amsl.com (Postfix) with ESMTP id 46BC93A68A0 for <iucg@ietf.org>; Mon,  5 Apr 2010 16:24:51 -0700 (PDT)
Received: from [95.176.69.185] (port=49695 helo=jfcmsc.jefsey.com) by montage2.altserver.com with esmtpa (Exim 4.69) (envelope-from <jefsey@jefsey.com>) id 1Nyvey-0001Kc-5N; Mon, 05 Apr 2010 16:24:49 -0700
Message-Id: <7.0.1.0.2.20100404210515.0652d8e0@jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Sun, 04 Apr 2010 21:32:02 +0200
To: At-Large Worldwide <at-large@atlarge-lists.icann.org>, At-Large Worldwide <at-large@atlarge-lists.icann.org>
From: jefsey <jefsey@jefsey.com>
In-Reply-To: <g2pf65fb55e1003311151o7eef138l519222c7273417d8@mail.gmail. com>
References: <k2u874c02a21003310521o36372e3z442edc8951d631ae@mail.gmail.com> <slrnhr6h1h.bs3.lutz@belenus.iks-jena.de> <j2y874c02a21003310832g22384112x1eea60f3f762d11@mail.gmail.com> <g2pf65fb55e1003311151o7eef138l519222c7273417d8@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage2.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: iucg@ietf.org
Subject: Re: [iucg] [At-Large] China censors facebook twitter & youtube web traffic world wide using US government DNS
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Apr 2010 23:24:52 -0000

At 20:51 31/03/2010, McTim wrote:
>I don't see how ICANN has to answer to you (or to anyone) for any 
>random MiM attack.

ICANN is in charge of the DNS operational stability. Either it is 
insured, or it is not. If it is not,

- its duty to its TLD operators is to ask the IETF a solution, and 
possibly to spur a response in calling for (1) a private study (2) a 
report to the GAC calling upon Governments to finance the 
corresponding R&D (cf. IAB RFC 3869).
- our own @large duty is to consider the best solution we may advise 
to our fellow users. This solution turns out being in line with the 
architectural precisions introduced through the IDNA example by the 
IESG for which I am provoking the necessary IAB guidance through an 
appeal. This should further on lead to a continuation of RFC 1959 and 
3439 about the Internet architecture (roughly the precision is that 
once reached a given threshold diversity cannot be supported by 
bandwidth increase but by (partly DNS embedded) metadata exchanges 
between user side metaprocessors).

Joe's advise of running his/her own root, is also the conclusion of 
the DNS-Operations people. This is also a part of the IUCG (Internet 
@larges at the IETF) investigated "Interplus" Internet Use Interface 
(IUI) architecture. However, the IUI implications also depend on 
other on-going IAB work. So, it is only fair for us to presently work 
on prototyping and testing, and reporting to the IAB.

Definitly our Internet lead users' point of view is that DNSSEC is an 
operational no go for us and would bring us no additional protection. 
This POV aslo seem to be shared by some DNSops contributors.

Best
jfc



From jefsey@jefsey.com  Sun Apr 18 09:52:47 2010
Return-Path: <jefsey@jefsey.com>
X-Original-To: iucg@core3.amsl.com
Delivered-To: iucg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A63C33A68D7 for <iucg@core3.amsl.com>; Sun, 18 Apr 2010 09:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.455
X-Spam-Level: **
X-Spam-Status: No, score=2.455 tagged_above=-999 required=5 tests=[AWL=3.565,  BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id teEvoSH+LB0z for <iucg@core3.amsl.com>; Sun, 18 Apr 2010 09:52:46 -0700 (PDT)
Received: from montage2.altserver.com (montage2.altserver.com [72.34.52.22]) by core3.amsl.com (Postfix) with ESMTP id E13EE3A6841 for <iucg@ietf.org>; Sun, 18 Apr 2010 09:52:46 -0700 (PDT)
Received: from [95.176.104.35] (port=55678 helo=jfcmsc.jefsey.com) by montage2.altserver.com with esmtpa (Exim 4.69) (envelope-from <jefsey@jefsey.com>) id 1O3XjZ-0005ZT-L9; Sun, 18 Apr 2010 09:52:38 -0700
Message-Id: <7.0.1.0.2.20100417232450.06fbe4b0@jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Sun, 18 Apr 2010 18:52:34 +0200
To: Matthew <muskrat7@gmail.com>
From: JFC Morfin <jefsey@jefsey.com>
In-Reply-To: <m2w9a3d16231004161207yb017360fz135df4fee1a14ee2@mail.gmail .com>
References: <m2w9a3d16231004161207yb017360fz135df4fee1a14ee2@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage2.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: iucg@ietf.org
Subject: Re: [iucg] Idea for IPv4 addition or extension
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Apr 2010 16:52:47 -0000

Dear Matthew,
the main user expectation is permanent IP address and global scope 
IDv6 (IPv6 interface ID).
I am not sure how your idea support this need.
jfc

At 21:07 16/04/2010, Matthew wrote:
>I would like to propose the following concept for discussion. The idea
>is to either extend IPv4 or create a new protocol that would work with
>IPv4 in order to allow a backwards compatible, yet hierarchical
>addressing model. The format is ruff and I wish others to evaluate its
>feasibility.
>
>The general layout of a fully-unique address follows:
>
><96-bit identifier based on region, service provider, etc> <32-bit
>IPv4 style address>
>
>In addition, organizations with an ASN would have the following
>fully-unique address:
>
><16 or 32-bit ASN> <96-bit ID> <32-bit IPv4 style address>
>
>ASN's could be registered to multiple Service Providers without making
>a large mess to the tables.
>
>Individual hosts would only use their IPv4 style address for local
>access and wouldn't need the full address unless talking outside their
>organization and/or ISP.
>
>Internet routing tables would only need 96-bit IDs and BGP tables
>would only need ASN to 96-bit ID mappings.
>
>When talking to a host that has an ASN you could get away with only
>sending to <ASN> + <IPv4 style address> since the ASN to 96-bit ID
>would be mapped on the Internet and the local ISP would then know
>where to route the IPv4 style address once it was within their area.
>
>This could be done by extending IPv4 or by creating a new protocol,
>i.e. Area Routing Protocol (AP for short).
>
>During transition, legacy IPv4 hosts would talk to a gateway device
>which would know its 96-bit ID and allow communication with the new
>protocol.
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf


From muskrat7@gmail.com  Sun Apr 18 17:06:25 2010
Return-Path: <muskrat7@gmail.com>
X-Original-To: iucg@core3.amsl.com
Delivered-To: iucg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0279E3A68B7 for <iucg@core3.amsl.com>; Sun, 18 Apr 2010 17:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uH7F4ByYn18N for <iucg@core3.amsl.com>; Sun, 18 Apr 2010 17:06:23 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id C3FCC3A67A6 for <iucg@ietf.org>; Sun, 18 Apr 2010 17:06:23 -0700 (PDT)
Received: by gwj20 with SMTP id 20so91224gwj.31 for <iucg@ietf.org>; Sun, 18 Apr 2010 17:06:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=xFb6lJC/Gvw2eCOCKnuMT3s2gScQK9eMsaByXIAWg1I=; b=eXZOY3o9gPi2MJu1IVALRMF5itjnXU/oLW96vt86F5+Jw2ErQmVqh5wdYuzkBgbeX1 OLSUMk6Xgep6EaAWyO/tAwfdl+zVvaRb7OZqtVhOEHc1zC+HEKKA9/z2lXF4wOEZQMRm EgP9Mf+b1/T5P3TG4VxuFnSAgq38VPuLPDWD4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=vaVlG+EeP+1u0K+J5c1Q3bXmnBizKNSltYd6VLA8VIv3nECpkfcPUJWg5rp504ozId 9PtY8n/JEkIXW/B4UbXgKdmRMFOki1DuOra+C7GR0uJFDRRTQNea/LoZeHszxsoMdfJv DwH+hI9WsIemF3uA42X/eVvLUcv2uTdcq9EWA=
Received: by 10.100.86.6 with SMTP id j6mr9171931anb.235.1271635572845; Sun, 18 Apr 2010 17:06:12 -0700 (PDT)
Received: from [192.168.1.110] (adsl-99-156-238-232.dsl.applwi.sbcglobal.net [99.156.238.232]) by mx.google.com with ESMTPS id 23sm4449656iwn.2.2010.04.18.17.06.11 (version=SSLv3 cipher=RC4-MD5); Sun, 18 Apr 2010 17:06:12 -0700 (PDT)
Message-ID: <4BCB9E71.6010609@gmail.com>
Date: Sun, 18 Apr 2010 19:06:09 -0500
From: Matthew <muskrat7@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: JFC Morfin <jefsey@jefsey.com>
References: <m2w9a3d16231004161207yb017360fz135df4fee1a14ee2@mail.gmail.com> <7.0.1.0.2.20100417232450.06fbe4b0@jefsey.com>
In-Reply-To: <7.0.1.0.2.20100417232450.06fbe4b0@jefsey.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 19 Apr 2010 00:54:05 -0700
Cc: iucg@ietf.org
Subject: Re: [iucg] Idea for IPv4 addition or extension
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Apr 2010 00:06:25 -0000

On 4/18/2010 11:52 AM, JFC Morfin wrote:
> Dear Matthew,
> the main user expectation is permanent IP address and global scope 
> IDv6 (IPv6 interface ID).
> I am not sure how your idea support this need.
> jfc
>

My main reason for this was to allow IPv4 backwards compatibility and to 
force summarization of sorts.

IDv6 could be accomplished by using 32-bits of the 96-bit ID to combine 
with the lower 32-bit IPv4 address.

I can think of too many examples throughout history when the expected 
outcome never happens and things end up right back where they were.

IPv6 will start out clean, then exception after exception will occur in 
order to allow organizations to do all sorts of crazy things. In 
addition, 100% IPv4 compatibility would be a great benefit.


> At 21:07 16/04/2010, Matthew wrote:
>> I would like to propose the following concept for discussion. The idea
>> is to either extend IPv4 or create a new protocol that would work with
>> IPv4 in order to allow a backwards compatible, yet hierarchical
>> addressing model. The format is ruff and I wish others to evaluate its
>> feasibility.
>>
>> The general layout of a fully-unique address follows:
>>
>> <96-bit identifier based on region, service provider, etc> <32-bit
>> IPv4 style address>
>>
>> In addition, organizations with an ASN would have the following
>> fully-unique address:
>>
>> <16 or 32-bit ASN> <96-bit ID> <32-bit IPv4 style address>
>>
>> ASN's could be registered to multiple Service Providers without making
>> a large mess to the tables.
>>
>> Individual hosts would only use their IPv4 style address for local
>> access and wouldn't need the full address unless talking outside their
>> organization and/or ISP.
>>
>> Internet routing tables would only need 96-bit IDs and BGP tables
>> would only need ASN to 96-bit ID mappings.
>>
>> When talking to a host that has an ASN you could get away with only
>> sending to <ASN> + <IPv4 style address> since the ASN to 96-bit ID
>> would be mapped on the Internet and the local ISP would then know
>> where to route the IPv4 style address once it was within their area.
>>
>> This could be done by extending IPv4 or by creating a new protocol,
>> i.e. Area Routing Protocol (AP for short).
>>
>> During transition, legacy IPv4 hosts would talk to a gateway device
>> which would know its 96-bit ID and allow communication with the new
>> protocol.
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>
>


From jefsey@jefsey.com  Mon Apr 19 00:57:47 2010
Return-Path: <jefsey@jefsey.com>
X-Original-To: iucg@core3.amsl.com
Delivered-To: iucg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D8A33A684C for <iucg@core3.amsl.com>; Mon, 19 Apr 2010 00:57:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.564
X-Spam-Level: *
X-Spam-Status: No, score=1.564 tagged_above=-999 required=5 tests=[AWL=2.674,  BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mypfgdJArcSU for <iucg@core3.amsl.com>; Mon, 19 Apr 2010 00:57:45 -0700 (PDT)
Received: from montage2.altserver.com (montage2.altserver.com [72.34.52.22]) by core3.amsl.com (Postfix) with ESMTP id 8899E3A684A for <iucg@ietf.org>; Mon, 19 Apr 2010 00:57:45 -0700 (PDT)
Received: from [95.176.104.35] (port=49607 helo=jfcmsc.jefsey.com) by montage2.altserver.com with esmtpa (Exim 4.69) (envelope-from <jefsey@jefsey.com>) id 1O3lrM-00047n-D2 for iucg@ietf.org; Mon, 19 Apr 2010 00:57:37 -0700
Message-Id: <7.0.1.0.2.20100419095449.05d84190@jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 19 Apr 2010 09:57:37 +0200
To: iucg@ietf.org
From: jefsey <jefsey@jefsey.com>
In-Reply-To: <m2w9a3d16231004161207yb017360fz135df4fee1a14ee2@mail.gmail .com> <4BC91574.5010608@gmail.com> <4BC917A7.4000805@gmail.com>
References: <m2w9a3d16231004161207yb017360fz135df4fee1a14ee2@mail.gmail.com> <m2w9a3d16231004161207yb017360fz135df4fee1a14ee2@mail.gmail.com> <4BC91574.5010608@gmail.com> <m2w9a3d16231004161207yb017360fz135df4fee1a14ee2@mail.gmail.com> <4BC91574.5010608@gmail.com> <4BC917A7.4000805@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage2.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: [iucg] Matthew's Idea for IPv4 addition or extension
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Apr 2010 07:57:47 -0000

Here is the mail background of the answer received from Matthew.
I will have some questions I will raise in another mail.

At 21:07 16/04/2010, Matthew wrote:
>I would like to propose the following concept for discussion. The idea
>is to either extend IPv4 or create a new protocol that would work with
>IPv4 in order to allow a backwards compatible, yet hierarchical
>addressing model. The format is ruff and I wish others to evaluate its
>feasibility.
>
>The general layout of a fully-unique address follows:
>
><96-bit identifier based on region, service provider, etc> <32-bit
>IPv4 style address>
>
>In addition, organizations with an ASN would have the following
>fully-unique address:
>
><16 or 32-bit ASN> <96-bit ID> <32-bit IPv4 style address>
>
>ASN's could be registered to multiple Service Providers without making
>a large mess to the tables.
>
>Individual hosts would only use their IPv4 style address for local
>access and wouldn't need the full address unless talking outside their
>organization and/or ISP.
>
>Internet routing tables would only need 96-bit IDs and BGP tables
>would only need ASN to 96-bit ID mappings.
>
>When talking to a host that has an ASN you could get away with only
>sending to <ASN> + <IPv4 style address> since the ASN to 96-bit ID
>would be mapped on the Internet and the local ISP would then know
>where to route the IPv4 style address once it was within their area.
>
>This could be done by extending IPv4 or by creating a new protocol,
>i.e. Area Routing Protocol (AP for short).
>
>During transition, legacy IPv4 hosts would talk to a gateway device
>which would know its 96-bit ID and allow communication with the new
>protocol.
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf

At 03:57 17/04/2010, Scott Brim wrote:
>Unfortunately there isn't much new under the sun.  This appears to be a
>combination of geographic addressing (various sources, e.g. Steve
>Deering and Tony Hain) and RFC1955.  Geographic addressing has
>deployability issues -- search for archives of those arguments.  The
>problem with mapping based on ASs is that they are the wrong granularity
>for external routing.  They are either too coarse (different prefixes
>within an AS need different treatment) or too fine.
>
>I've CCed the Routing Research Group.  I suggest you take further
>discussion there, but remember what's said about mud-wrestling with a pig.
>
>Scott
>
>Matthew allegedly wrote on 04/16/2010 15:07 EDT:
> > I would like to propose the following concept for discussion. The idea
> > is to either extend IPv4 or create a new protocol that would work with
> > IPv4 in order to allow a backwards compatible, yet hierarchical
> > addressing model. The format is ruff and I wish others to evaluate its
> > feasibility.
> >
> > The general layout of a fully-unique address follows:
> >
> > <96-bit identifier based on region, service provider, etc> <32-bit
> > IPv4 style address>
> >
> > In addition, organizations with an ASN would have the following
> > fully-unique address:
> >
> > <16 or 32-bit ASN> <96-bit ID> <32-bit IPv4 style address>
> >
> > ASN's could be registered to multiple Service Providers without making
> > a large mess to the tables.
> >
> > Individual hosts would only use their IPv4 style address for local
> > access and wouldn't need the full address unless talking outside their
> > organization and/or ISP.
> >
> > Internet routing tables would only need 96-bit IDs and BGP tables
> > would only need ASN to 96-bit ID mappings.
> >
> > When talking to a host that has an ASN you could get away with only
> > sending to <ASN> + <IPv4 style address> since the ASN to 96-bit ID
> > would be mapped on the Internet and the local ISP would then know
> > where to route the IPv4 style address once it was within their area.
> >
> > This could be done by extending IPv4 or by creating a new protocol,
> > i.e. Area Routing Protocol (AP for short).
> >
> > During transition, legacy IPv4 hosts would talk to a gateway device
> > which would know its 96-bit ID and allow communication with the new
> > protocol.
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf

At 04:06 17/04/2010, Matthew wrote:
>Thanks for the comments and the forward to rrg@irtf.org.
>
>Geographic was just an example; I left it intentionally vague for 
>discussion purposes.
>
>It partially borrows from OSI's addressing but with the twist of 
>full IPv4 address support and the fact that there are at least 3 
>distinct parts to the full address which can be used independently. 
>If you look closely it also has some DNS type qualities as well, but 
>my main vision is to have an address structure that more mimics 
>other forms of addressing while making ISPs the network entities 
>that each supply their full set(s) of IPv4 address space; while 
>maintaining complete backward compatibility with IPv4 during migrations.
>
>Thanks again, and I'll direct future discussions to the referenced list.
>
>
>-- Matt
>
>
>
>On 4/16/2010 8:57 PM, Scott Brim wrote:
>>Unfortunately there isn't much new under the sun.  This appears to be a
>>combination of geographic addressing (various sources, e.g. Steve
>>Deering and Tony Hain) and RFC1955.  Geographic addressing has
>>deployability issues -- search for archives of those arguments.  The
>>problem with mapping based on ASs is that they are the wrong granularity
>>for external routing.  They are either too coarse (different prefixes
>>within an AS need different treatment) or too fine.
>>
>>I've CCed the Routing Research Group.  I suggest you take further
>>discussion there, but remember what's said about mud-wrestling with a pig.
>>
>>Scott
>>
>>Matthew allegedly wrote on 04/16/2010 15:07 EDT:
>>
>>>I would like to propose the following concept for discussion. The idea
>>>is to either extend IPv4 or create a new protocol that would work with
>>>IPv4 in order to allow a backwards compatible, yet hierarchical
>>>addressing model. The format is ruff and I wish others to evaluate its
>>>feasibility.
>>>
>>>The general layout of a fully-unique address follows:
>>>
>>><96-bit identifier based on region, service provider, etc>  <32-bit
>>>IPv4 style address>
>>>
>>>In addition, organizations with an ASN would have the following
>>>fully-unique address:
>>>
>>><16 or 32-bit ASN>  <96-bit ID>  <32-bit IPv4 style address>
>>>
>>>ASN's could be registered to multiple Service Providers without making
>>>a large mess to the tables.
>>>
>>>Individual hosts would only use their IPv4 style address for local
>>>access and wouldn't need the full address unless talking outside their
>>>organization and/or ISP.
>>>
>>>Internet routing tables would only need 96-bit IDs and BGP tables
>>>would only need ASN to 96-bit ID mappings.
>>>
>>>When talking to a host that has an ASN you could get away with only
>>>sending to<ASN>  +<IPv4 style address>  since the ASN to 96-bit ID
>>>would be mapped on the Internet and the local ISP would then know
>>>where to route the IPv4 style address once it was within their area.
>>>
>>>This could be done by extending IPv4 or by creating a new protocol,
>>>i.e. Area Routing Protocol (AP for short).
>>>
>>>During transition, legacy IPv4 hosts would talk to a gateway device
>>>which would know its 96-bit ID and allow communication with the new
>>>protocol.
>>>_______________________________________________
>>>Ietf mailing list
>>>Ietf@ietf.org
>>>https://www.ietf.org/mailman/listinfo/ietf
>>>
>>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf


From jefsey@jefsey.com  Mon Apr 19 17:25:20 2010
Return-Path: <jefsey@jefsey.com>
X-Original-To: iucg@core3.amsl.com
Delivered-To: iucg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 669593A68EA for <iucg@core3.amsl.com>; Mon, 19 Apr 2010 17:25:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.285
X-Spam-Level: 
X-Spam-Status: No, score=0.285 tagged_above=-999 required=5 tests=[AWL=2.883,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qpn+cPskEexC for <iucg@core3.amsl.com>; Mon, 19 Apr 2010 17:25:17 -0700 (PDT)
Received: from montage2.altserver.com (montage2.altserver.com [72.34.52.22]) by core3.amsl.com (Postfix) with ESMTP id 54E523A68B0 for <iucg@ietf.org>; Mon, 19 Apr 2010 17:25:17 -0700 (PDT)
Received: from [95.176.104.35] (port=53809 helo=jfcmsc.jefsey.com) by montage2.altserver.com with esmtpa (Exim 4.69) (envelope-from <jefsey@jefsey.com>) id 1O41H0-00018T-1p; Mon, 19 Apr 2010 17:25:08 -0700
Message-Id: <7.0.1.0.2.20100419102728.05d84568@jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Tue, 20 Apr 2010 02:25:06 +0200
To: internet users contributing group <iucg@ietf.org>
From: JFC Morfin <jefsey@jefsey.com>
In-Reply-To: <7.0.1.0.2.20100419095449.05d84190@jefsey.com>
References: <m2w9a3d16231004161207yb017360fz135df4fee1a14ee2@mail.gmail.com> <m2w9a3d16231004161207yb017360fz135df4fee1a14ee2@mail.gmail.com> <4BC91574.5010608@gmail.com> <m2w9a3d16231004161207yb017360fz135df4fee1a14ee2@mail.gmail.com> <4BC91574.5010608@gmail.com> <4BC917A7.4000805@gmail.com> <7.0.1.0.2.20100419095449.05d84190@jefsey.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_93035829==.ALT"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage2.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: Matthew <muskrat7@gmail.com>
Subject: Re: [iucg] Matthew's Idea for IPv4 addition or extension
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Apr 2010 00:25:20 -0000

--=====================_93035829==.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit

At 09:57 19/04/2010, jefsey wrote:
>Here is the mail background of the answer received from Matthew.
>I will have some questions I will raise in another mail.

 From what I gather, Matthew, your idea is to split what could also 
be an IPv6 address into a header and an IPv4 address. This is a 
numbering plan organization? Initially there were five of them left 
free (IPv4, IPv6 IETF and multicast being documented - using the 
first 3 bits), ITU as a candidate for managing one. I am not sure if 
these are still the case with the IETF's lack of "state of current 
dreams" report.

Your idea is not far from (could be included in) the one I proposed 
some years ago - which is briefly documented (in French) at 
<http://afrac.org/uninum.pdf>http://afrac.org/uninum.pdf - I could 
not comment on it today :-) as I do not recall everything, and it has 
an <http://uninum.org/>http://uninum.org IUCG preparatory page.

There are, as usual, three approaches from:

(1) incremental, from RFCs:  IETF/IRTF concerning the entire Internet
(2) disruptive, from the state of the art: engineers being upset 
about the lack of an IETF accepted solution and proposing one
(3) architectural, from reality: the users' expectations and 
propositions based upon their needed practical open generalized 
simplifications (what IUCG is meant to discuss and propose).

Basically, "the UNINUM proposition is a universal open root for all 
the digital namespaces and the smart automated uses of their 
numbering plans. That universal open root is just an open format that 
permits one to unlimitedly number unique numbering plans. To that, 
the UNINUM numbering plan number (NPN, numéro de plan de numération) 
can then be associated with specialized functions and "paradata" 
(i.e. parallel information, [as thoseMatthew proposes] - such as 
location, confidence, credibility levels, dates of validation, 
certification by registry authorities, crossverification schemes, 
memory translation data; etc.). It can also be proposed resolution 
services, such as resolving the IPv6 address for an IPv4 address or 
vice versa for cross addressing or LISP approaches".

I did not push into that because the priority was to have the 
Internet multiplication architectural solution defined and confirmed. 
Now that it is exemplified by IDNA2008, we need to get it 
acknowledged by the IETF. The IESG response to my appeal is halfway 
through this process. Before proceeding further in the Interplus 
architecture, where UNINUM and its resolution process have their 
part, I would prefer the IAB position on all of this to be clarified 
(or officially delayed). The IESG response is already doing part of 
that, but IAB is the real authority.

The reason for that is the Internet is not in a position to deliver 
most of what we expected from it. However, we clearly know today just 
how it will do it: in using peripheral metaprocesses that are 
organized in an Internet Use Interface (IUI). Our, partly worked out, 
IUI Interplus architecture addresses that need. However, it has to 
use some universal resources that could interfere with IANA's 
resources (presentations, classes, etc.), and that need to be 
administered by someone. This someone has not yet been identified. 
This is why (however it does not change a single bit in any existing 
protocols) it is not entirely neutral to the IETF Internet 
standardization process, which is guided by the IAB.

jfc

>At 21:07 16/04/2010, Matthew wrote:
>>I would like to propose the following concept for discussion. The idea
>>is to either extend IPv4 or create a new protocol that would work with
>>IPv4 in order to allow a backwards compatible, yet hierarchical
>>addressing model. The format is ruff and I wish others to evaluate its
>>feasibility.
>>
>>The general layout of a fully-unique address follows:
>>
>><96-bit identifier based on region, service provider, etc> <32-bit
>>IPv4 style address>
>>
>>In addition, organizations with an ASN would have the following
>>fully-unique address:
>>
>><16 or 32-bit ASN> <96-bit ID> <32-bit IPv4 style address>
>>
>>ASN's could be registered to multiple Service Providers without making
>>a large mess to the tables.
>>
>>Individual hosts would only use their IPv4 style address for local
>>access and wouldn't need the full address unless talking outside their
>>organization and/or ISP.
>>
>>Internet routing tables would only need 96-bit IDs and BGP tables
>>would only need ASN to 96-bit ID mappings.
>>
>>When talking to a host that has an ASN you could get away with only
>>sending to <ASN> + <IPv4 style address> since the ASN to 96-bit ID
>>would be mapped on the Internet and the local ISP would then know
>>where to route the IPv4 style address once it was within their area.
>>
>>This could be done by extending IPv4 or by creating a new protocol,
>>i.e. Area Routing Protocol (AP for short).
>>
>>During transition, legacy IPv4 hosts would talk to a gateway device
>>which would know its 96-bit ID and allow communication with the new
>>protocol.
>>_______________________________________________
>>Ietf mailing list
>>Ietf@ietf.org
>>https://www.ietf.org/mailman/listinfo/ietf
>
>At 03:57 17/04/2010, Scott Brim wrote:
>>Unfortunately there isn't much new under the sun.  This appears to be a
>>combination of geographic addressing (various sources, e.g. Steve
>>Deering and Tony Hain) and RFC1955.  Geographic addressing has
>>deployability issues -- search for archives of those arguments.  The
>>problem with mapping based on ASs is that they are the wrong granularity
>>for external routing.  They are either too coarse (different prefixes
>>within an AS need different treatment) or too fine.
>>
>>I've CCed the Routing Research Group.  I suggest you take further
>>discussion there, but remember what's said about mud-wrestling with a pig.
>>
>>Scott
>>
>>Matthew allegedly wrote on 04/16/2010 15:07 EDT:
>> > I would like to propose the following concept for discussion. The idea
>> > is to either extend IPv4 or create a new protocol that would work with
>> > IPv4 in order to allow a backwards compatible, yet hierarchical
>> > addressing model. The format is ruff and I wish others to evaluate its
>> > feasibility.
>> >
>> > The general layout of a fully-unique address follows:
>> >
>> > <96-bit identifier based on region, service provider, etc> <32-bit
>> > IPv4 style address>
>> >
>> > In addition, organizations with an ASN would have the following
>> > fully-unique address:
>> >
>> > <16 or 32-bit ASN> <96-bit ID> <32-bit IPv4 style address>
>> >
>> > ASN's could be registered to multiple Service Providers without making
>> > a large mess to the tables.
>> >
>> > Individual hosts would only use their IPv4 style address for local
>> > access and wouldn't need the full address unless talking outside their
>> > organization and/or ISP.
>> >
>> > Internet routing tables would only need 96-bit IDs and BGP tables
>> > would only need ASN to 96-bit ID mappings.
>> >
>> > When talking to a host that has an ASN you could get away with only
>> > sending to <ASN> + <IPv4 style address> since the ASN to 96-bit ID
>> > would be mapped on the Internet and the local ISP would then know
>> > where to route the IPv4 style address once it was within their area.
>> >
>> > This could be done by extending IPv4 or by creating a new protocol,
>> > i.e. Area Routing Protocol (AP for short).
>> >
>> > During transition, legacy IPv4 hosts would talk to a gateway device
>> > which would know its 96-bit ID and allow communication with the new
>> > protocol.
>> > _______________________________________________
>> > Ietf mailing list
>> > Ietf@ietf.org
>> > https://www.ietf.org/mailman/listinfo/ietf
>>_______________________________________________
>>Ietf mailing list
>>Ietf@ietf.org
>>https://www.ietf.org/mailman/listinfo/ietf
>
>At 04:06 17/04/2010, Matthew wrote:
>>Thanks for the comments and the forward to rrg@irtf.org.
>>
>>Geographic was just an example; I left it intentionally vague for 
>>discussion purposes.
>>
>>It partially borrows from OSI's addressing but with the twist of 
>>full IPv4 address support and the fact that there are at least 3 
>>distinct parts to the full address which can be used independently. 
>>If you look closely it also has some DNS type qualities as well, 
>>but my main vision is to have an address structure that more mimics 
>>other forms of addressing while making ISPs the network entities 
>>that each supply their full set(s) of IPv4 address space; while 
>>maintaining complete backward compatibility with IPv4 during migrations.
>>
>>Thanks again, and I'll direct future discussions to the referenced list.
>>
>>
>>-- Matt
>>
>>
>>
>>On 4/16/2010 8:57 PM, Scott Brim wrote:
>>>Unfortunately there isn't much new under the sun.  This appears to be a
>>>combination of geographic addressing (various sources, e.g. Steve
>>>Deering and Tony Hain) and RFC1955.  Geographic addressing has
>>>deployability issues -- search for archives of those arguments.  The
>>>problem with mapping based on ASs is that they are the wrong granularity
>>>for external routing.  They are either too coarse (different prefixes
>>>within an AS need different treatment) or too fine.
>>>
>>>I've CCed the Routing Research Group.  I suggest you take further
>>>discussion there, but remember what's said about mud-wrestling with a pig.
>>>
>>>Scott
>>>
>>>Matthew allegedly wrote on 04/16/2010 15:07 EDT:
>>>
>>>>I would like to propose the following concept for discussion. The idea
>>>>is to either extend IPv4 or create a new protocol that would work with
>>>>IPv4 in order to allow a backwards compatible, yet hierarchical
>>>>addressing model. The format is ruff and I wish others to evaluate its
>>>>feasibility.
>>>>
>>>>The general layout of a fully-unique address follows:
>>>>
>>>><96-bit identifier based on region, service provider, etc>  <32-bit
>>>>IPv4 style address>
>>>>
>>>>In addition, organizations with an ASN would have the following
>>>>fully-unique address:
>>>>
>>>><16 or 32-bit ASN>  <96-bit ID>  <32-bit IPv4 style address>
>>>>
>>>>ASN's could be registered to multiple Service Providers without making
>>>>a large mess to the tables.
>>>>
>>>>Individual hosts would only use their IPv4 style address for local
>>>>access and wouldn't need the full address unless talking outside their
>>>>organization and/or ISP.
>>>>
>>>>Internet routing tables would only need 96-bit IDs and BGP tables
>>>>would only need ASN to 96-bit ID mappings.
>>>>
>>>>When talking to a host that has an ASN you could get away with only
>>>>sending to<ASN>  +<IPv4 style address>  since the ASN to 96-bit ID
>>>>would be mapped on the Internet and the local ISP would then know
>>>>where to route the IPv4 style address once it was within their area.
>>>>
>>>>This could be done by extending IPv4 or by creating a new protocol,
>>>>i.e. Area Routing Protocol (AP for short).
>>>>
>>>>During transition, legacy IPv4 hosts would talk to a gateway device
>>>>which would know its 96-bit ID and allow communication with the new
>>>>protocol.
>>>>_______________________________________________
>>>>Ietf mailing list
>>>>Ietf@ietf.org
>>>>https://www.ietf.org/mailman/listinfo/ietf
>>
>>_______________________________________________
>>Ietf mailing list
>>Ietf@ietf.org
>>https://www.ietf.org/mailman/listinfo/ietf
>
>_______________________________________________
>iucg mailing list
>iucg@ietf.org
>https://www.ietf.org/mailman/listinfo/iucg

--=====================_93035829==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

<html>
<body>
At 09:57 19/04/2010, jefsey wrote:<br>
<blockquote type=cite class=cite cite="">Here is the mail background of
the answer received from Matthew.<br>
I will have some questions I will raise in another
mail.</blockquote><br>
 From what I gather, Matthew, your idea is to split what could also be an
IPv6 address into a header and an IPv4 address. This is a numbering plan
organization? Initially there were five of them left free (IPv4, IPv6
IETF and multicast being documented - using the first 3 bits), ITU as a
candidate for managing one. I am not sure if these are still the case
with the IETF's lack of &quot;state of current dreams&quot;
report.<br><br>
Your idea is not far from (could be included in) the one I proposed some
years ago - which is briefly documented (in French) at
<a href="http://afrac.org/uninum.pdf">http://afrac.org/uninum.pdf</a> - I
could not comment on it today :-) as I do not recall everything, and it
has an <a href="http://uninum.org/">http://uninum.org</a> IUCG
preparatory page.<br><br>
There are, as usual, three approaches from:<br><br>
(1) incremental, from RFCs:&nbsp; IETF/IRTF concerning the entire
Internet<br>
(2) disruptive, from the state of the art: engineers being upset about
the lack of an IETF accepted solution and proposing one&nbsp; <br>
(3) architectural, from reality: the users’ expectations and propositions
based upon their needed practical open generalized simplifications (what
IUCG is meant to discuss and propose).<br><br>
Basically, &quot;the UNINUM proposition is a universal open root for all
the digital namespaces and the smart automated uses of their numbering
plans. That universal open root is just an open format that permits one
to unlimitedly number unique numbering plans. To that, the UNINUM
numbering plan number (NPN, numéro de plan de numération) can then be
associated with specialized functions and “paradata” (i.e. parallel
information, [as thoseMatthew proposes] - such as location, confidence,
credibility levels, dates of validation, certification by registry
authorities, crossverification schemes, memory translation data; etc.).
It can also be proposed resolution services, such as resolving the IPv6
address for an IPv4 address or vice versa for cross addressing or LISP
approaches&quot;. <br><br>
I did not push into that because the priority was to have the Internet
multiplication architectural solution defined and confirmed. Now that it
is exemplified by IDNA2008, we need to get it acknowledged by the IETF.
The IESG response to my appeal is halfway through this process. Before
proceeding further in the Interplus architecture, where UNINUM and its
resolution process have their part, I would prefer the IAB position on
all of this to be clarified (or officially delayed). The IESG response is
already doing part of that, but IAB is the real authority.<br><br>
The reason for that is the Internet is not in a position to deliver most
of what we expected from it. However, we clearly know today just how it
will do it: in using peripheral metaprocesses that are organized in an
Internet Use Interface (IUI). Our, partly worked out, IUI Interplus
architecture addresses that need. However, it has to use some universal
resources that could interfere with IANA’s resources (presentations,
classes, etc.), and that need to be administered by someone. This someone
has not yet been identified. This is why (however it does not change a
single bit in any existing protocols) it is not entirely neutral to the
IETF Internet standardization process, which is guided by the
IAB.<br><br>
jfc<br><br>
<blockquote type=cite class=cite cite="">At 21:07 16/04/2010, Matthew
wrote:<br>
<blockquote type=cite class=cite cite="">I would like to propose the
following concept for discussion. The idea<br>
is to either extend IPv4 or create a new protocol that would work
with<br>
IPv4 in order to allow a backwards compatible, yet hierarchical<br>
addressing model. The format is ruff and I wish others to evaluate
its<br>
feasibility.<br><br>
The general layout of a fully-unique address follows:<br><br>
&lt;96-bit identifier based on region, service provider, etc&gt;
&lt;32-bit<br>
IPv4 style address&gt;<br><br>
In addition, organizations with an ASN would have the following<br>
fully-unique address:<br><br>
&lt;16 or 32-bit ASN&gt; &lt;96-bit ID&gt; &lt;32-bit IPv4 style
address&gt;<br><br>
ASN's could be registered to multiple Service Providers without
making<br>
a large mess to the tables.<br><br>
Individual hosts would only use their IPv4 style address for local<br>
access and wouldn't need the full address unless talking outside
their<br>
organization and/or ISP.<br><br>
Internet routing tables would only need 96-bit IDs and BGP tables<br>
would only need ASN to 96-bit ID mappings.<br><br>
When talking to a host that has an ASN you could get away with only<br>
sending to &lt;ASN&gt; + &lt;IPv4 style address&gt; since the ASN to
96-bit ID<br>
would be mapped on the Internet and the local ISP would then know<br>
where to route the IPv4 style address once it was within their
area.<br><br>
This could be done by extending IPv4 or by creating a new protocol,<br>
i.e. Area Routing Protocol (AP for short).<br><br>
During transition, legacy IPv4 hosts would talk to a gateway device<br>
which would know its 96-bit ID and allow communication with the new<br>
protocol.<br>
_______________________________________________<br>
Ietf mailing list<br>
Ietf@ietf.org<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf" eudora="autourl">
https://www.ietf.org/mailman/listinfo/ietf</a></blockquote><br>
At 03:57 17/04/2010, Scott Brim wrote:<br>
<blockquote type=cite class=cite cite="">Unfortunately there isn't much
new under the sun.&nbsp; This appears to be a<br>
combination of geographic addressing (various sources, e.g. Steve<br>
Deering and Tony Hain) and RFC1955.&nbsp; Geographic addressing has<br>
deployability issues -- search for archives of those arguments.&nbsp;
The<br>
problem with mapping based on ASs is that they are the wrong
granularity<br>
for external routing.&nbsp; They are either too coarse (different
prefixes<br>
within an AS need different treatment) or too fine.<br><br>
I've CCed the Routing Research Group.&nbsp; I suggest you take
further<br>
discussion there, but remember what's said about mud-wrestling with a
pig.<br><br>
Scott<br><br>
Matthew allegedly wrote on 04/16/2010 15:07 EDT:<br>
&gt; I would like to propose the following concept for discussion. The
idea<br>
&gt; is to either extend IPv4 or create a new protocol that would work
with<br>
&gt; IPv4 in order to allow a backwards compatible, yet hierarchical<br>
&gt; addressing model. The format is ruff and I wish others to evaluate
its<br>
&gt; feasibility.<br>
&gt;<br>
&gt; The general layout of a fully-unique address follows:<br>
&gt;<br>
&gt; &lt;96-bit identifier based on region, service provider, etc&gt;
&lt;32-bit<br>
&gt; IPv4 style address&gt;<br>
&gt;<br>
&gt; In addition, organizations with an ASN would have the following<br>
&gt; fully-unique address:<br>
&gt;<br>
&gt; &lt;16 or 32-bit ASN&gt; &lt;96-bit ID&gt; &lt;32-bit IPv4 style
address&gt;<br>
&gt;<br>
&gt; ASN's could be registered to multiple Service Providers without
making<br>
&gt; a large mess to the tables.<br>
&gt;<br>
&gt; Individual hosts would only use their IPv4 style address for
local<br>
&gt; access and wouldn't need the full address unless talking outside
their<br>
&gt; organization and/or ISP.<br>
&gt;<br>
&gt; Internet routing tables would only need 96-bit IDs and BGP
tables<br>
&gt; would only need ASN to 96-bit ID mappings.<br>
&gt;<br>
&gt; When talking to a host that has an ASN you could get away with
only<br>
&gt; sending to &lt;ASN&gt; + &lt;IPv4 style address&gt; since the ASN to
96-bit ID<br>
&gt; would be mapped on the Internet and the local ISP would then
know<br>
&gt; where to route the IPv4 style address once it was within their
area.<br>
&gt;<br>
&gt; This could be done by extending IPv4 or by creating a new
protocol,<br>
&gt; i.e. Area Routing Protocol (AP for short).<br>
&gt;<br>
&gt; During transition, legacy IPv4 hosts would talk to a gateway
device<br>
&gt; which would know its 96-bit ID and allow communication with the
new<br>
&gt; protocol.<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; Ietf@ietf.org<br>
&gt;
<a href="https://www.ietf.org/mailman/listinfo/ietf" eudora="autourl">
https://www.ietf.org/mailman/listinfo/ietf</a><br>
_______________________________________________<br>
Ietf mailing list<br>
Ietf@ietf.org<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf" eudora="autourl">
https://www.ietf.org/mailman/listinfo/ietf</a></blockquote><br>
At 04:06 17/04/2010, Matthew wrote:<br>
<blockquote type=cite class=cite cite="">Thanks for the comments and the
forward to rrg@irtf.org.<br><br>
Geographic was just an example; I left it intentionally vague for
discussion purposes.<br><br>
It partially borrows from OSI's addressing but with the twist of full
IPv4 address support and the fact that there are at least 3 distinct
parts to the full address which can be used independently. If you look
closely it also has some DNS type qualities as well, but my main vision
is to have an address structure that more mimics other forms of
addressing while making ISPs the network entities that each supply their
full set(s) of IPv4 address space; while maintaining complete backward
compatibility with IPv4 during migrations.<br><br>
Thanks again, and I'll direct future discussions to the referenced
list.<br><br>
<br>
-- Matt<br><br>
<br><br>
On 4/16/2010 8:57 PM, Scott Brim wrote:<br>
<blockquote type=cite class=cite cite="">Unfortunately there isn't much
new under the sun.&nbsp; This appears to be a<br>
combination of geographic addressing (various sources, e.g. Steve<br>
Deering and Tony Hain) and RFC1955.&nbsp; Geographic addressing has<br>
deployability issues -- search for archives of those arguments.&nbsp;
The<br>
problem with mapping based on ASs is that they are the wrong
granularity<br>
for external routing.&nbsp; They are either too coarse (different
prefixes<br>
within an AS need different treatment) or too fine.<br><br>
I've CCed the Routing Research Group.&nbsp; I suggest you take
further<br>
discussion there, but remember what's said about mud-wrestling with a
pig.<br><br>
Scott<br><br>
Matthew allegedly wrote on 04/16/2010 15:07 EDT:<br><br>
<blockquote type=cite class=cite cite="">I would like to propose the
following concept for discussion. The idea<br>
is to either extend IPv4 or create a new protocol that would work
with<br>
IPv4 in order to allow a backwards compatible, yet hierarchical<br>
addressing model. The format is ruff and I wish others to evaluate
its<br>
feasibility.<br><br>
The general layout of a fully-unique address follows:<br><br>
&lt;96-bit identifier based on region, service provider, etc&gt;&nbsp;
&lt;32-bit<br>
IPv4 style address&gt;<br><br>
In addition, organizations with an ASN would have the following<br>
fully-unique address:<br><br>
&lt;16 or 32-bit ASN&gt;&nbsp; &lt;96-bit ID&gt;&nbsp; &lt;32-bit IPv4
style address&gt;<br><br>
ASN's could be registered to multiple Service Providers without
making<br>
a large mess to the tables.<br>
<br>
Individual hosts would only use their IPv4 style address for local<br>
access and wouldn't need the full address unless talking outside
their<br>
organization and/or ISP.<br><br>
Internet routing tables would only need 96-bit IDs and BGP tables<br>
would only need ASN to 96-bit ID mappings.<br><br>
When talking to a host that has an ASN you could get away with only<br>
sending to&lt;ASN&gt;&nbsp; +&lt;IPv4 style address&gt;&nbsp; since the
ASN to 96-bit ID<br>
would be mapped on the Internet and the local ISP would then know<br>
where to route the IPv4 style address once it was within their
area.<br><br>
This could be done by extending IPv4 or by creating a new protocol,<br>
i.e. Area Routing Protocol (AP for short).<br><br>
During transition, legacy IPv4 hosts would talk to a gateway device<br>
which would know its 96-bit ID and allow communication with the new<br>
protocol.<br>
_______________________________________________<br>
Ietf mailing list<br>
Ietf@ietf.org<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf" eudora="autourl">
https://www.ietf.org/mailman/listinfo/ietf</a></blockquote></blockquote>
<br>
_______________________________________________<br>
Ietf mailing list<br>
Ietf@ietf.org<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf" eudora="autourl">
https://www.ietf.org/mailman/listinfo/ietf</a></blockquote><br>
_______________________________________________<br>
iucg mailing list<br>
iucg@ietf.org<br>
<a href="https://www.ietf.org/mailman/listinfo/iucg" eudora="autourl">
https://www.ietf.org/mailman/listinfo/iucg</a></blockquote></body>
</html>

--=====================_93035829==.ALT--


From jefsey@jefsey.com  Tue Apr 20 12:28:47 2010
Return-Path: <jefsey@jefsey.com>
X-Original-To: iucg@core3.amsl.com
Delivered-To: iucg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B2CB3A6951 for <iucg@core3.amsl.com>; Tue, 20 Apr 2010 12:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.104
X-Spam-Level: *
X-Spam-Status: No, score=1.104 tagged_above=-999 required=5 tests=[AWL=1.103,  BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pI7BOHopHqSl for <iucg@core3.amsl.com>; Tue, 20 Apr 2010 12:28:46 -0700 (PDT)
Received: from montage2.altserver.com (montage2.altserver.com [72.34.52.22]) by core3.amsl.com (Postfix) with ESMTP id 8688F3A6828 for <iucg@ietf.org>; Tue, 20 Apr 2010 12:28:46 -0700 (PDT)
Received: from [95.176.104.35] (port=52837 helo=jfcmsc.jefsey.com) by montage2.altserver.com with esmtpa (Exim 4.69) (envelope-from <jefsey@jefsey.com>) id 1O4J7c-0001AS-Hp; Tue, 20 Apr 2010 12:28:37 -0700
Message-Id: <7.0.1.0.2.20100420212157.059bf820@jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Tue, 20 Apr 2010 21:28:34 +0200
To: Bob Braden <braden@ISI.EDU>
From: jefsey <jefsey@jefsey.com>
In-Reply-To: <350E7285-D153-4E3B-BDF2-DFF1277DA7CC@iab.org>
References: <350E7285-D153-4E3B-BDF2-DFF1277DA7CC@iab.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage2.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: iucg@ietf.org
Subject: Re: [iucg] Glenn Kowack now formally RFC Series Editor (RSE)
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Apr 2010 19:28:47 -0000

Dear Bob,
thank you for all the work you already acheived for all of us.
jfc

On 17:13 20/04/2010, IAB Chair said:
>Dear Colleagues,
>
>I am happy to announce that Bob Braden and Glenn Kowack have 
>completed the handoff of the RFC Series Editor (RSE) role on schedule.
>After 30 June, Bob Braden will continue his involvement in the 
>series through the RSAG, of which he is already a member.  This 
>approach, and the strong cooperation of all the players, is 
>permitting a seamless transition and maintaining the continuity of 
>the RFC Series.  With the completion of this formal appointment, the 
>RFC Editor model advances yet another step.


From jefsey@jefsey.com  Sat Apr 24 01:46:59 2010
Return-Path: <jefsey@jefsey.com>
X-Original-To: iucg@core3.amsl.com
Delivered-To: iucg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 734033A687F; Sat, 24 Apr 2010 01:46:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.166
X-Spam-Level: *
X-Spam-Status: No, score=1.166 tagged_above=-999 required=5 tests=[AWL=0.565,  BAYES_50=0.001, J_CHICKENPOX_73=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KA2yif6k6mkg; Sat, 24 Apr 2010 01:46:58 -0700 (PDT)
Received: from montage2.altserver.com (montage2.altserver.com [72.34.52.22]) by core3.amsl.com (Postfix) with ESMTP id B84C83A6808; Sat, 24 Apr 2010 01:46:57 -0700 (PDT)
Received: from [95.176.50.96] (port=62346 helo=jfcmsc.jefsey.com) by montage2.altserver.com with esmtpa (Exim 4.69) (envelope-from <jefsey@jefsey.com>) id 1O5b0b-0005SN-D2; Sat, 24 Apr 2010 01:46:42 -0700
Message-Id: <7.0.1.0.2.20100424104536.072f2518@jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Sat, 24 Apr 2010 10:46:56 +0200
To: Peter Saint-Andre <stpeter@stpeter.im>,newprep@ietf.org
From: jefsey <jefsey@jefsey.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage2.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IDNA2010 Documentation <workon@idna2010.org>, iucg@ietf.org
Subject: Re: [iucg] [newprep] Fwd: I-D Action:draft-resman-idna2008-mappings-01.txt
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Apr 2010 08:46:59 -0000

At 16:40 22/04/2010, Peter Saint-Andre wrote:
>This document is probably of interest here...
>
>-------- Original Message --------
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-resman-idna2008-mappings-01.txt

This document is important. As important as the IAB's 
http://tools.ietf.org/html/draft-iab-idn-encoding-01 and possibly the 
tedious but comprehensive enough 
(http://www.ietf.org/iesg/appeal/morfin-2010-03-10.pdf) compilation 
of my IESG level appeal for those wanting to get the details and 
grasp the whole context.

My reading of the concerned parts of IDNA2008 is, as I have explained 
many times, that it was necessary for a domain name character set 
(DNCS) to eventually be worked out. It was adequately formed in using 
ISO 10646 code points, which permits easy interoperability. I, 
therefore, understand the process, which is being used to prepare a 
UCS string into a DNCS string, as a "domainization". A remaining 
difficulty is, however, the support of Latin language majuscules, 
since they are necessary for their semantic addressing.

In addition, I consider the DNCS in-parts as a super-set of a 
"regular character set" ("regcode") prepared in the same manner, but 
also with anti-phishing considerations, so that the resulting charset 
can serve as a secure man/machine multiorthotypographic universal 
charset (passports, security cards, operating system commands, 
databases, ISO 11179 registriesetc.). A secure "regcode" encoding 
table should eventually be produced that could be based upon Unicode 
+ lingual context and be attached to ISO 3166 and use ccTAGs for a 
unique secure international sorting order that could be used in 
"internatioperable" applications. This would permit an IETF regcode 
to address the Internet protocols' needs through a standard 
"regularization" process, and to free Unicode from network operations 
constraints.

This issue will be raised as one of the points of my IAB level 
appeal, because IDNA2008 was (per its charter and by its results) a 
severance of the Internet from Unicode. The responses to the 
questions legitimately raised by your proposed charter do in fact 
belong to the IAB guidance that I claim IESG should have requested 
before approving IDNA2008 - or quoted in a disclaimer indicating that 
IDNA2008 is the network side of multilingualization, not the whole of it.

Some consider that the other part belongs to the UI (User Interface, 
cf. "resman" draft). I personally think that it also belongs to the 
needed architectural IUI (Internet Usage Interface) if one wants to 
respect the constraints investigated by the IAB in its Domain 
Internationalization draft. Anyway, through UI or IUI, the work you 
consider is necessary. However, I would not engage in it, before the 
IAB has published its position on the matter. This is why I 
documented and am following my Project.FRA roadmap to the IESG, and 
they have discussed it before approving IDNA2008.

Their response to my appeal shows that they also accept that the 
issue is worth a BoF (or several ones since your concern is not the 
only one that should be consistently investigated). However, until 
IAB has commented on the IESG answer, I do not really know in which 
area (if any) such IUI related issues (including yours) should be 
discussed. Please remember that IAB has initiated a Draft on IDNs 
that, at least for the time being, seems to contradict the very 
IDNA2003 architectural principle of IDN in Applications and lead to 
consider an IDNApplication that would certainly impact your 
evaluation process. Basically, one cannot have _several_ software 
modules in a computer that may convert and resolve domain names differently.

Best.

_______________________________________________
newprep mailing list
newprep@ietf.org
https://www.ietf.org/mailman/listinfo/newprep


From yaojk@cnnic.cn  Sat Apr 24 17:45:03 2010
Return-Path: <yaojk@cnnic.cn>
X-Original-To: iucg@core3.amsl.com
Delivered-To: iucg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D35F3A682F for <iucg@core3.amsl.com>; Sat, 24 Apr 2010 17:45:03 -0700 (PDT)
X-Quarantine-ID: <B4SmjtNelJHk>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER, Duplicate header field: "Message-ID"
X-Spam-Flag: NO
X-Spam-Score: 2.904
X-Spam-Level: **
X-Spam-Status: No, score=2.904 tagged_above=-999 required=5 tests=[AWL=-0.253,  BAYES_50=0.001, J_CHICKENPOX_73=0.6, MIME_BASE64_TEXT=1.753, MSGID_FROM_MTA_HEADER=0.803]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B4SmjtNelJHk for <iucg@core3.amsl.com>; Sat, 24 Apr 2010 17:45:03 -0700 (PDT)
Received: from cnnic.cn (smtp.cnnic.cn [159.226.7.146]) by core3.amsl.com (Postfix) with SMTP id 6B4BF3A6855 for <iucg@ietf.org>; Sat, 24 Apr 2010 17:45:00 -0700 (PDT)
Received: (eyou send program); Sun, 25 Apr 2010 08:44:49 +0800
Message-ID: <472156289.10196@cnnic.cn>
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown (HELO abc) (127.0.0.1) by 127.0.0.1 with SMTP; Sun, 25 Apr 2010 08:44:49 +0800
Message-ID: <3C2EC311A8C445C49F7696FBF4630ECB@abc>
From: "Yao Jiankang" <yaojk@cnnic.cn>
To: "jefsey" <jefsey@jefsey.com>, "Peter Saint-Andre" <stpeter@stpeter.im>, <newprep@ietf.org>
References: <7.0.1.0.2.20100424104536.072f2518@jefsey.com>
Date: Sun, 25 Apr 2010 08:44:44 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Mailman-Approved-At: Sun, 25 Apr 2010 04:50:36 -0700
Cc: IDNA2010 Documentation <workon@idna2010.org>, iucg@ietf.org
Subject: Re: [iucg] [newprep] Fwd: I-D Action:draft-resman-idna2008-mappings-01.txt
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Apr 2010 00:45:03 -0000

DQpXaGF0IHBldGVyIHNhaWQgaXMgIlRoaXMgZG9jdW1lbnQgaXMgcHJvYmFibHkgb2YgaW50ZXJl
c3QgaGVyZS4uLiIuDQpXZSBkbyBub3QgZm9jdXMgb24gSUROLCBidXQgaW50ZXJuYXRpb25hbGl6
ZWQgc3RyaW5nLiBUaGVyZSBpcyBhIGRpZmZlcmVuY2UuDQoNCg0KLS0tLS0gT3JpZ2luYWwgTWVz
c2FnZSAtLS0tLSANCkZyb206ICJqZWZzZXkiIDxqZWZzZXlAamVmc2V5LmNvbT4NClRvOiAiUGV0
ZXIgU2FpbnQtQW5kcmUiIDxzdHBldGVyQHN0cGV0ZXIuaW0+OyA8bmV3cHJlcEBpZXRmLm9yZz4N
CkNjOiAiSUROQTIwMTAgRG9jdW1lbnRhdGlvbiIgPHdvcmtvbkBpZG5hMjAxMC5vcmc+OyA8aXVj
Z0BpZXRmLm9yZz4NClNlbnQ6IFNhdHVyZGF5LCBBcHJpbCAyNCwgMjAxMCA0OjQ2IFBNDQpTdWJq
ZWN0OiBSZTogW25ld3ByZXBdIEZ3ZDogSS1EIEFjdGlvbjpkcmFmdC1yZXNtYW4taWRuYTIwMDgt
bWFwcGluZ3MtMDEudHh0DQoNCg0KPiBBdCAxNjo0MCAyMi8wNC8yMDEwLCBQZXRlciBTYWludC1B
bmRyZSB3cm90ZToNCj4+VGhpcyBkb2N1bWVudCBpcyBwcm9iYWJseSBvZiBpbnRlcmVzdCBoZXJl
Li4uDQo+Pg0KPj4tLS0tLS0tLSBPcmlnaW5hbCBNZXNzYWdlIC0tLS0tLS0tDQo+PkEgVVJMIGZv
ciB0aGlzIEludGVybmV0LURyYWZ0IGlzOg0KPj5odHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0
LWRyYWZ0cy9kcmFmdC1yZXNtYW4taWRuYTIwMDgtbWFwcGluZ3MtMDEudHh0DQo+IA0KPiBUaGlz
IGRvY3VtZW50IGlzIGltcG9ydGFudC4gQXMgaW1wb3J0YW50IGFzIHRoZSBJQUIncyANCj4gaHR0
cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWFiLWlkbi1lbmNvZGluZy0wMSBhbmQgcG9z
c2libHkgdGhlIA0KPiB0ZWRpb3VzIGJ1dCBjb21wcmVoZW5zaXZlIGVub3VnaCANCj4gKGh0dHA6
Ly93d3cuaWV0Zi5vcmcvaWVzZy9hcHBlYWwvbW9yZmluLTIwMTAtMDMtMTAucGRmKSBjb21waWxh
dGlvbiANCj4gb2YgbXkgSUVTRyBsZXZlbCBhcHBlYWwgZm9yIHRob3NlIHdhbnRpbmcgdG8gZ2V0
IHRoZSBkZXRhaWxzIGFuZCANCj4gZ3Jhc3AgdGhlIHdob2xlIGNvbnRleHQuDQo+IA0KPiBNeSBy
ZWFkaW5nIG9mIHRoZSBjb25jZXJuZWQgcGFydHMgb2YgSUROQTIwMDggaXMsIGFzIEkgaGF2ZSBl
eHBsYWluZWQgDQo+IG1hbnkgdGltZXMsIHRoYXQgaXQgd2FzIG5lY2Vzc2FyeSBmb3IgYSBkb21h
aW4gbmFtZSBjaGFyYWN0ZXIgc2V0IA0KPiAoRE5DUykgdG8gZXZlbnR1YWxseSBiZSB3b3JrZWQg
b3V0LiBJdCB3YXMgYWRlcXVhdGVseSBmb3JtZWQgaW4gdXNpbmcgDQo+IElTTyAxMDY0NiBjb2Rl
IHBvaW50cywgd2hpY2ggcGVybWl0cyBlYXN5IGludGVyb3BlcmFiaWxpdHkuIEksIA0KPiB0aGVy
ZWZvcmUsIHVuZGVyc3RhbmQgdGhlIHByb2Nlc3MsIHdoaWNoIGlzIGJlaW5nIHVzZWQgdG8gcHJl
cGFyZSBhIA0KPiBVQ1Mgc3RyaW5nIGludG8gYSBETkNTIHN0cmluZywgYXMgYSAiZG9tYWluaXph
dGlvbiIuIEEgcmVtYWluaW5nIA0KPiBkaWZmaWN1bHR5IGlzLCBob3dldmVyLCB0aGUgc3VwcG9y
dCBvZiBMYXRpbiBsYW5ndWFnZSBtYWp1c2N1bGVzLCANCj4gc2luY2UgdGhleSBhcmUgbmVjZXNz
YXJ5IGZvciB0aGVpciBzZW1hbnRpYyBhZGRyZXNzaW5nLg0KPiANCj4gSW4gYWRkaXRpb24sIEkg
Y29uc2lkZXIgdGhlIEROQ1MgaW4tcGFydHMgYXMgYSBzdXBlci1zZXQgb2YgYSANCj4gInJlZ3Vs
YXIgY2hhcmFjdGVyIHNldCIgKCJyZWdjb2RlIikgcHJlcGFyZWQgaW4gdGhlIHNhbWUgbWFubmVy
LCBidXQgDQo+IGFsc28gd2l0aCBhbnRpLXBoaXNoaW5nIGNvbnNpZGVyYXRpb25zLCBzbyB0aGF0
IHRoZSByZXN1bHRpbmcgY2hhcnNldCANCj4gY2FuIHNlcnZlIGFzIGEgc2VjdXJlIG1hbi9tYWNo
aW5lIG11bHRpb3J0aG90eXBvZ3JhcGhpYyB1bml2ZXJzYWwgDQo+IGNoYXJzZXQgKHBhc3Nwb3J0
cywgc2VjdXJpdHkgY2FyZHMsIG9wZXJhdGluZyBzeXN0ZW0gY29tbWFuZHMsIA0KPiBkYXRhYmFz
ZXMsIElTTyAxMTE3OSByZWdpc3RyaWVzZXRjLikuIEEgc2VjdXJlICJyZWdjb2RlIiBlbmNvZGlu
ZyANCj4gdGFibGUgc2hvdWxkIGV2ZW50dWFsbHkgYmUgcHJvZHVjZWQgdGhhdCBjb3VsZCBiZSBi
YXNlZCB1cG9uIFVuaWNvZGUgDQo+ICsgbGluZ3VhbCBjb250ZXh0IGFuZCBiZSBhdHRhY2hlZCB0
byBJU08gMzE2NiBhbmQgdXNlIGNjVEFHcyBmb3IgYSANCj4gdW5pcXVlIHNlY3VyZSBpbnRlcm5h
dGlvbmFsIHNvcnRpbmcgb3JkZXIgdGhhdCBjb3VsZCBiZSB1c2VkIGluIA0KPiAiaW50ZXJuYXRp
b3BlcmFibGUiIGFwcGxpY2F0aW9ucy4gVGhpcyB3b3VsZCBwZXJtaXQgYW4gSUVURiByZWdjb2Rl
IA0KPiB0byBhZGRyZXNzIHRoZSBJbnRlcm5ldCBwcm90b2NvbHMnIG5lZWRzIHRocm91Z2ggYSBz
dGFuZGFyZCANCj4gInJlZ3VsYXJpemF0aW9uIiBwcm9jZXNzLCBhbmQgdG8gZnJlZSBVbmljb2Rl
IGZyb20gbmV0d29yayBvcGVyYXRpb25zIA0KPiBjb25zdHJhaW50cy4NCj4gDQo+IFRoaXMgaXNz
dWUgd2lsbCBiZSByYWlzZWQgYXMgb25lIG9mIHRoZSBwb2ludHMgb2YgbXkgSUFCIGxldmVsIA0K
PiBhcHBlYWwsIGJlY2F1c2UgSUROQTIwMDggd2FzIChwZXIgaXRzIGNoYXJ0ZXIgYW5kIGJ5IGl0
cyByZXN1bHRzKSBhIA0KPiBzZXZlcmFuY2Ugb2YgdGhlIEludGVybmV0IGZyb20gVW5pY29kZS4g
VGhlIHJlc3BvbnNlcyB0byB0aGUgDQo+IHF1ZXN0aW9ucyBsZWdpdGltYXRlbHkgcmFpc2VkIGJ5
IHlvdXIgcHJvcG9zZWQgY2hhcnRlciBkbyBpbiBmYWN0IA0KPiBiZWxvbmcgdG8gdGhlIElBQiBn
dWlkYW5jZSB0aGF0IEkgY2xhaW0gSUVTRyBzaG91bGQgaGF2ZSByZXF1ZXN0ZWQgDQo+IGJlZm9y
ZSBhcHByb3ZpbmcgSUROQTIwMDggLSBvciBxdW90ZWQgaW4gYSBkaXNjbGFpbWVyIGluZGljYXRp
bmcgdGhhdCANCj4gSUROQTIwMDggaXMgdGhlIG5ldHdvcmsgc2lkZSBvZiBtdWx0aWxpbmd1YWxp
emF0aW9uLCBub3QgdGhlIHdob2xlIG9mIGl0Lg0KPiANCj4gU29tZSBjb25zaWRlciB0aGF0IHRo
ZSBvdGhlciBwYXJ0IGJlbG9uZ3MgdG8gdGhlIFVJIChVc2VyIEludGVyZmFjZSwgDQo+IGNmLiAi
cmVzbWFuIiBkcmFmdCkuIEkgcGVyc29uYWxseSB0aGluayB0aGF0IGl0IGFsc28gYmVsb25ncyB0
byB0aGUgDQo+IG5lZWRlZCBhcmNoaXRlY3R1cmFsIElVSSAoSW50ZXJuZXQgVXNhZ2UgSW50ZXJm
YWNlKSBpZiBvbmUgd2FudHMgdG8gDQo+IHJlc3BlY3QgdGhlIGNvbnN0cmFpbnRzIGludmVzdGln
YXRlZCBieSB0aGUgSUFCIGluIGl0cyBEb21haW4gDQo+IEludGVybmF0aW9uYWxpemF0aW9uIGRy
YWZ0LiBBbnl3YXksIHRocm91Z2ggVUkgb3IgSVVJLCB0aGUgd29yayB5b3UgDQo+IGNvbnNpZGVy
IGlzIG5lY2Vzc2FyeS4gSG93ZXZlciwgSSB3b3VsZCBub3QgZW5nYWdlIGluIGl0LCBiZWZvcmUg
dGhlIA0KPiBJQUIgaGFzIHB1Ymxpc2hlZCBpdHMgcG9zaXRpb24gb24gdGhlIG1hdHRlci4gVGhp
cyBpcyB3aHkgSSANCj4gZG9jdW1lbnRlZCBhbmQgYW0gZm9sbG93aW5nIG15IFByb2plY3QuRlJB
IHJvYWRtYXAgdG8gdGhlIElFU0csIGFuZCANCj4gdGhleSBoYXZlIGRpc2N1c3NlZCBpdCBiZWZv
cmUgYXBwcm92aW5nIElETkEyMDA4Lg0KPiANCj4gVGhlaXIgcmVzcG9uc2UgdG8gbXkgYXBwZWFs
IHNob3dzIHRoYXQgdGhleSBhbHNvIGFjY2VwdCB0aGF0IHRoZSANCj4gaXNzdWUgaXMgd29ydGgg
YSBCb0YgKG9yIHNldmVyYWwgb25lcyBzaW5jZSB5b3VyIGNvbmNlcm4gaXMgbm90IHRoZSANCj4g
b25seSBvbmUgdGhhdCBzaG91bGQgYmUgY29uc2lzdGVudGx5IGludmVzdGlnYXRlZCkuIEhvd2V2
ZXIsIHVudGlsIA0KPiBJQUIgaGFzIGNvbW1lbnRlZCBvbiB0aGUgSUVTRyBhbnN3ZXIsIEkgZG8g
bm90IHJlYWxseSBrbm93IGluIHdoaWNoIA0KPiBhcmVhIChpZiBhbnkpIHN1Y2ggSVVJIHJlbGF0
ZWQgaXNzdWVzIChpbmNsdWRpbmcgeW91cnMpIHNob3VsZCBiZSANCj4gZGlzY3Vzc2VkLiBQbGVh
c2UgcmVtZW1iZXIgdGhhdCBJQUIgaGFzIGluaXRpYXRlZCBhIERyYWZ0IG9uIElETnMgDQo+IHRo
YXQsIGF0IGxlYXN0IGZvciB0aGUgdGltZSBiZWluZywgc2VlbXMgdG8gY29udHJhZGljdCB0aGUg
dmVyeSANCj4gSUROQTIwMDMgYXJjaGl0ZWN0dXJhbCBwcmluY2lwbGUgb2YgSUROIGluIEFwcGxp
Y2F0aW9ucyBhbmQgbGVhZCB0byANCj4gY29uc2lkZXIgYW4gSUROQXBwbGljYXRpb24gdGhhdCB3
b3VsZCBjZXJ0YWlubHkgaW1wYWN0IHlvdXIgDQo+IGV2YWx1YXRpb24gcHJvY2Vzcy4gQmFzaWNh
bGx5LCBvbmUgY2Fubm90IGhhdmUgX3NldmVyYWxfIHNvZnR3YXJlIA0KPiBtb2R1bGVzIGluIGEg
Y29tcHV0ZXIgdGhhdCBtYXkgY29udmVydCBhbmQgcmVzb2x2ZSBkb21haW4gbmFtZXMgZGlmZmVy
ZW50bHkuDQo+IA0KPiBCZXN0Lg0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4gbmV3cHJlcCBtYWlsaW5nIGxpc3QNCj4gbmV3cHJlcEBpZXRm
Lm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL25ld3ByZXANCj4g
DQo+IA0KPg==


From jefsey@jefsey.com  Sun Apr 25 05:31:14 2010
Return-Path: <jefsey@jefsey.com>
X-Original-To: iucg@core3.amsl.com
Delivered-To: iucg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CEE4C3A6A60; Sun, 25 Apr 2010 05:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.103
X-Spam-Level: *
X-Spam-Status: No, score=1.103 tagged_above=-999 required=5 tests=[AWL=0.502,  BAYES_50=0.001, J_CHICKENPOX_73=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1dTlqdaJSdQ8; Sun, 25 Apr 2010 05:31:13 -0700 (PDT)
Received: from montage2.altserver.com (montage2.altserver.com [72.34.52.22]) by core3.amsl.com (Postfix) with ESMTP id D11773A692D; Sun, 25 Apr 2010 05:31:12 -0700 (PDT)
Received: from [95.176.50.96] (port=65512 helo=jfcmsc.jefsey.com) by montage2.altserver.com with esmtpa (Exim 4.69) (envelope-from <jefsey@jefsey.com>) id 1O60z9-0007La-MT; Sun, 25 Apr 2010 05:30:57 -0700
Message-Id: <7.0.1.0.2.20100425135047.05ae4e60@jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Sun, 25 Apr 2010 14:30:54 +0200
To: "Yao Jiankang" <yaojk@cnnic.cn>, "Peter Saint-Andre" <stpeter@stpeter.im>,<newprep@ietf.org>
From: jefsey <jefsey@jefsey.com>
In-Reply-To: <472156289.10196@cnnic.cn>
References: <7.0.1.0.2.20100424104536.072f2518@jefsey.com> <472156289.10196@cnnic.cn>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage2.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: IDNA2010 Documentation <workon@idna2010.org>, iucg@ietf.org
Subject: Re: [iucg] [newprep] Fwd: I-D Action:draft-resman-idna2008-mappings-01.txt
X-BeenThere: iucg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: internet users contributing group <iucg@ietf.org>
List-Id: internet users contributing group <iucg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/iucg>
List-Post: <mailto:iucg@ietf.org>
List-Help: <mailto:iucg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iucg>, <mailto:iucg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Apr 2010 12:31:14 -0000

At 02:44 25/04/2010, Yao Jiankang wrote:

>What peter said is "This document is probably of interest here...".
>We do not focus on IDN, but internationalized string. There is a difference.

I think that the first thing to be done is to consider if the 
intended works is to be a set of patches, or to fit in the Internet 
architecture which is now based upon RFC 1958, RFC 3439 and IDNA2008.

I am only interested in the later. This is why I disagree with the 
ambiguous "internationalized string" wording. Because we should not 
necessarily replicate alternative solutions (RFC 1958) and because we 
also should strive for the simplest one (RFC 3439), if we want this 
work to be of use, we need to discuss universal services character 
sets. The target is to support a multilingual universal networked 
system, where IETF so far has tried to diversely internationalize 
functions of an ASCII network system. Today, based upon experience we 
reached the point where the IDNA2008 character set seems a good 
enough working basis for such a multilingual universal network system 
character set. For clarity sake I call if regcode (regular code) and 
its use in replacement of another system, "regularization".

I can already list as constraints: "user readyness", interoperability 
with ASCII and ISO 10646 code points, usability by IDNApplications 
(users side) and IDNA (network side), as being much phishing proof as 
possible, orthotypographically acceptable (no semantic value having 
to be bent/lost due to regcode constraints) and to be unambiguously 
multilingually/scripturally sortable throughout all the digital 
ecosystem (for example in being able to be used with my ccTAG 
proposition). I also add as a major constraint: its universal 
usability by IUI slots, what implies a common adminance. In a 
nutshell we need a world digital ecosystem equivalent to ASCII (when 
UCS is a complete CS for typographers).

As I explained, at this stage I am questioning the IETF through a 
possible three steps process (appeal to IESG and IAB, possibly ISOC 
further to experimental operations) in order to know (1) in which 
kind of Internet architectural understanding should it now operate 
(2) who should lead that adminance (because precisely we do not focus 
on IDN, and even not on network issues) and on which grounds.  This 
leads to a very simple question: should we adapt a code to existing 
functions, or adapt protocols and functions to a code - and then which code?

jfc


>----- Original Message -----
>From: "jefsey" <jefsey@jefsey.com>
>To: "Peter Saint-Andre" <stpeter@stpeter.im>; <newprep@ietf.org>
>Cc: "IDNA2010 Documentation" <workon@idna2010.org>; <iucg@ietf.org>
>Sent: Saturday, April 24, 2010 4:46 PM
>Subject: Re: [newprep] Fwd: I-D Action:draft-resman-idna2008-mappings-01.txt
>
>
> > At 16:40 22/04/2010, Peter Saint-Andre wrote:
> >>This document is probably of interest here...
> >>
> >>-------- Original Message --------
> >>A URL for this Internet-Draft is:
> >>http://www.ietf.org/internet-drafts/draft-resman-idna2008-mappings-01.txt
> >
> > This document is important. As important as the IAB's
> > http://tools.ietf.org/html/draft-iab-idn-encoding-01 and possibly the
> > tedious but comprehensive enough
> > (http://www.ietf.org/iesg/appeal/morfin-2010-03-10.pdf) compilation
> > of my IESG level appeal for those wanting to get the details and
> > grasp the whole context.
> >
> > My reading of the concerned parts of IDNA2008 is, as I have explained
> > many times, that it was necessary for a domain name character set
> > (DNCS) to eventually be worked out. It was adequately formed in using
> > ISO 10646 code points, which permits easy interoperability. I,
> > therefore, understand the process, which is being used to prepare a
> > UCS string into a DNCS string, as a "domainization". A remaining
> > difficulty is, however, the support of Latin language majuscules,
> > since they are necessary for their semantic addressing.
> >
> > In addition, I consider the DNCS in-parts as a super-set of a
> > "regular character set" ("regcode") prepared in the same manner, but
> > also with anti-phishing considerations, so that the resulting charset
> > can serve as a secure man/machine multiorthotypographic universal
> > charset (passports, security cards, operating system commands,
> > databases, ISO 11179 registriesetc.). A secure "regcode" encoding
> > table should eventually be produced that could be based upon Unicode
> > + lingual context and be attached to ISO 3166 and use ccTAGs for a
> > unique secure international sorting order that could be used in
> > "internatioperable" applications. This would permit an IETF regcode
> > to address the Internet protocols' needs through a standard
> > "regularization" process, and to free Unicode from network operations
> > constraints.
> >
> > This issue will be raised as one of the points of my IAB level
> > appeal, because IDNA2008 was (per its charter and by its results) a
> > severance of the Internet from Unicode. The responses to the
> > questions legitimately raised by your proposed charter do in fact
> > belong to the IAB guidance that I claim IESG should have requested
> > before approving IDNA2008 - or quoted in a disclaimer indicating that
> > IDNA2008 is the network side of multilingualization, not the whole of it.
> >
> > Some consider that the other part belongs to the UI (User Interface,
> > cf. "resman" draft). I personally think that it also belongs to the
> > needed architectural IUI (Internet Usage Interface) if one wants to
> > respect the constraints investigated by the IAB in its Domain
> > Internationalization draft. Anyway, through UI or IUI, the work you
> > consider is necessary. However, I would not engage in it, before the
> > IAB has published its position on the matter. This is why I
> > documented and am following my Project.FRA roadmap to the IESG, and
> > they have discussed it before approving IDNA2008.
> >
> > Their response to my appeal shows that they also accept that the
> > issue is worth a BoF (or several ones since your concern is not the
> > only one that should be consistently investigated). However, until
> > IAB has commented on the IESG answer, I do not really know in which
> > area (if any) such IUI related issues (including yours) should be
> > discussed. Please remember that IAB has initiated a Draft on IDNs
> > that, at least for the time being, seems to contradict the very
> > IDNA2003 architectural principle of IDN in Applications and lead to
> > consider an IDNApplication that would certainly impact your
> > evaluation process. Basically, one cannot have _several_ software
> > modules in a computer that may convert and resolve domain names 
> differently.
> >
> > Best.
> >
> > _______________________________________________
> > newprep mailing list
> > newprep@ietf.org
> > https://www.ietf.org/mailman/listinfo/newprep
> >
> >
> >

