Re: SIP Addressing Limitations

"Paul Francis (formerly Paul Tsuchiya" <francis@thumper.bellcore.com> Wed, 19 May 1993 20:40 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10089; 19 May 93 16:40 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10085; 19 May 93 16:40 EDT
Received: from thumper.bellcore.com by CNRI.Reston.VA.US id aa25934; 19 May 93 16:40 EDT
Received: by thumper.bellcore.com (4.1/4.7) id <AA28713> for ietf-archive@nri.reston.va.us; Wed, 19 May 93 16:40:20 EDT
Received: from tsuchiya.bellcore.com by thumper.bellcore.com (4.1/4.7) id <AA28476> for /usr/lib/sendmail -oi -fowner-pip X-pip; Wed, 19 May 93 16:38:49 EDT
Received: by tsuchiya.bellcore.com (4.1/4.7) id <AA04035> for whyman@mwassocs.demon.co.uk; Wed, 19 May 93 16:38:49 EDT
Date: Wed, 19 May 93 16:38:49 EDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Paul Francis (formerly Paul Tsuchiya" <francis@thumper.bellcore.com>
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Message-Id: <9305192038.AA04035@tsuchiya.bellcore.com>
To: bsimpson@morningstar.com, whyman@mwassocs.demon.co.uk
Subject: Re: SIP Addressing Limitations
Cc: pip@thumper.bellcore.com, sip@caldera.usc.edu, tuba@lanl.gov

>  
>  Some of the other commenters on the SIP list have been too polite.
>  
>  Perhaps you should actually READ my proposed plan (based on > 100 hours
>  of my work, considerable work and thought by Steve Deering, and many
>  comments by others).  You can find it in *sip-64bit-plan*, at any
>  internet-drafts directory.
>  
>  Comments and improvements are welcome.
>  

In preparation for making some comments on this message,
I took another look at the plan, and found some things
confusing.  In particular, I can't understand the idea of
clustering, and how that allows for provider assignments.
I'm not even sure how to formulate questions, but let me
start with this......

Given the following:

                                                        - ---- ---- ----
   Netherlands         15.3    16.7   0.6  C001 0000 010. ....
   Belgium              9.9    10.5   0.1  C001 0000 0110 ....
   Luxembourg           0.39    0.5e  1.1  C001 0000 0111 0000 0... ....
                                                     ---- ---- ---- ----
   United Kingdom      57.8    61.0   0.3  C001 0001 0... ....
   Ireland              3.5     5.0  -0.3  C001 0001 1000 0...
   Guernsey&Jersey(UK)  0.16    0.2e  0.8  C001 0001 1000 1000 00.. ....
   Isle of Man (UK)     0.064   <.1e  0.1  C001 0001 1000 1000 010. ....
                                                      --- ---- ---- ----

Am I to deduce that Ireland, Guernsey&Jersey, and the Isle of Man
are clustered?  I'm interpreting the dashes as indicating the
bits that are not common between the clustered countries.  The
UK has a 0 at the beginning of the second byte, and the other
three have a 1 at the beginning of the second byte, thus I
conclude that the UK is not clustered with the other three.
But, this doesn't seem to follow common sense, so maybe I'm
wrong.

There is a statement that the clustering will facilitate
provider based allocation, but I don't understand this
(The quote is "This division provides the primary intersection
between metropolitan and provider based allocation.  Approximately
1/4 to 1/2 of the numbers in each cluster are reserved for
provider based allocation and future expansion."

Could you give me an example of how a provider would be
assigned in the context of the above-mentioned cluster?

Thanks,

PX