From owner-grow@lists.uoregon.edu  Fri Apr  1 13:38:21 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25088
	for <grow-archive@lists.ietf.org>; Fri, 1 Apr 2005 13:38:21 -0500 (EST)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j31IXHGX027873;
	Fri, 1 Apr 2005 10:33:17 -0800 (PST)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j31IXHF1027872;
	Fri, 1 Apr 2005 10:33:17 -0800 (PST)
Received: from felix.automagic.org (felix.hopcount.ca [204.152.186.101])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j31IXGYP027842
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <grow@lists.uoregon.edu>; Fri, 1 Apr 2005 10:33:16 -0800 (PST)
Received: from [199.212.90.16] (helo=[199.212.90.16])
	by felix.automagic.org with esmtpsa (TLSv1:RC4-SHA:128)
	(Exim 4.42 (FreeBSD))
	id 1DHQxI-000BZP-1I
	for grow@lists.uoregon.edu; Fri, 01 Apr 2005 18:33:16 +0000
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Transfer-Encoding: 7bit
Message-Id: <e881939938c2c4c6d84496d9ef296c46@isc.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: grow@lists.uoregon.edu
From: Joe Abley <jabley@isc.org>
Subject: grow: ipv6 anycast
Date: Fri, 1 Apr 2005 13:32:44 -0500
X-Mailer: Apple Mail (2.619.2)
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi all,

Following comments at the meeting in Minneapolis regarding the conflict  
between draft-ietf-grow-anycast and the v6 addressing spec (which  
imposes a prohibition on v6 anycast) I wrote up the following:

    
http://www.ietf.org/internet-drafts/draft-jabley-v6-anycast-clarify 
-00.txt

This document might be seen as a companion to a revised  
draft-ietf-grow-anycast, removing the v6 anycast prohibition such that  
the anycast document is no longer at odds with the current v6 spec.

Comments on this approach (and the draft) would be most welcome.


Joe

_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Mon Apr  4 08:38:29 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26402
	for <grow-archive@lists.ietf.org>; Mon, 4 Apr 2005 08:38:28 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j34CZHf0015292;
	Mon, 4 Apr 2005 05:35:17 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j34CZHmw015291;
	Mon, 4 Apr 2005 05:35:17 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j34CZEQX015254
	for <grow@lists.uoregon.edu>; Mon, 4 Apr 2005 05:35:15 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j34CZ5g28504;
	Mon, 4 Apr 2005 15:35:06 +0300
Date: Mon, 4 Apr 2005 15:35:05 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Joe Abley <jabley@isc.org>
cc: grow@lists.uoregon.edu, ipv6@ietf.org
Subject: Re: grow: ipv6 anycast
In-Reply-To: <e881939938c2c4c6d84496d9ef296c46@isc.org>
Message-ID: <Pine.LNX.4.61.0504041532270.27464@netcore.fi>
References: <e881939938c2c4c6d84496d9ef296c46@isc.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Joe,

This is a timely topic, because IPv6 WG just less than week ago 
forwarded the revision of the addressing architecture to be published 
as Draft Standard. (IPv6 WG is Cc:ed.)

That draft, 
http://www.ietf.org/internet-drafts/draft-ietf-ipv6-addr-arch-v4-02.txt 
still has the problematic wording wrt anycast addresses.

On Fri, 1 Apr 2005, Joe Abley wrote:
> Following comments at the meeting in Minneapolis regarding the conflict 
> between draft-ietf-grow-anycast and the v6 addressing spec (which imposes a 
> prohibition on v6 anycast) I wrote up the following:
>
>  http://www.ietf.org/internet-drafts/draft-jabley-v6-anycast-clarify-00.txt
>
> This document might be seen as a companion to a revised 
> draft-ietf-grow-anycast, removing the v6 anycast prohibition such that the 
> anycast document is no longer at odds with the current v6 spec.
>
> Comments on this approach (and the draft) would be most welcome.
>
>
> Joe
>
> _________________________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
> web archive:        http://darkwing.uoregon.edu/~llynch/grow/
>

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Mon Apr  4 22:14:52 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06858
	for <grow-archive@lists.ietf.org>; Mon, 4 Apr 2005 22:14:51 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j352CbN5006136;
	Mon, 4 Apr 2005 19:12:37 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j352Cbxh006135;
	Mon, 4 Apr 2005 19:12:37 -0700 (PDT)
Received: from felix.automagic.org (felix.hopcount.ca [204.152.186.101])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j352Cav2006121
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <grow@lists.uoregon.edu>; Mon, 4 Apr 2005 19:12:37 -0700 (PDT)
Received: from [199.212.90.16] (helo=[199.212.90.16])
	by felix.automagic.org with esmtpsa (TLSv1:RC4-SHA:128)
	(Exim 4.42 (FreeBSD))
	id 1DIdYQ-000Ok9-Vg; Tue, 05 Apr 2005 02:12:35 +0000
In-Reply-To: <Pine.LNX.4.61.0504041532270.27464@netcore.fi>
References: <e881939938c2c4c6d84496d9ef296c46@isc.org> <Pine.LNX.4.61.0504041532270.27464@netcore.fi>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <9586cbecf7e3c931aec2cec835eda5a3@isc.org>
Content-Transfer-Encoding: 7bit
Cc: grow@lists.uoregon.edu, ipv6@ietf.org
From: Joe Abley <jabley@isc.org>
Subject: Re: grow: ipv6 anycast
Date: Mon, 4 Apr 2005 22:12:02 -0400
To: Pekka Savola <pekkas@netcore.fi>
X-Mailer: Apple Mail (2.619.2)
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 4 Apr 2005, at 08:35, Pekka Savola wrote:

> This is a timely topic, because IPv6 WG just less than week ago  
> forwarded the revision of the addressing architecture to be published  
> as Draft Standard. (IPv6 WG is Cc:ed.)
>
> That draft,  
> http://www.ietf.org/internet-drafts/draft-ietf-ipv6-addr-arch-v4 
> -02.txt still has the problematic wording wrt anycast addresses.

Yes, I noticed that. I sent mail to the authors of that draft asking  
them for their thoughts on the anycast issue, but I haven't heard  
anything back, yet.

Assuming there is consensus that v6 anycast for host-based services is  
a fait accompli, and that further prohibition is unnecessary, it would  
seem that adjusting the relevant paragraph in the revised (v4) v6  
addressing spec would be the cleanest way of proceeding.

However, although I think we had some kind of consensus to that effect  
in the grow meeting in Minneapolis, I haven't heard any opinion from  
those ipv6-wg folks who don't also participate in grow. Seems like some  
kind of hum from the ipv6 floor would be useful to hear (or, if no hum,  
active throwing of furniture).


Joe

_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr  5 07:06:40 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06484
	for <grow-archive@lists.ietf.org>; Tue, 5 Apr 2005 07:06:40 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j35B0FiG014420;
	Tue, 5 Apr 2005 04:00:15 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j35B0FLr014413;
	Tue, 5 Apr 2005 04:00:15 -0700 (PDT)
Received: from jhuapl.edu (piper.jhuapl.edu [128.244.26.33])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j35B0EG0014210
	for <grow@lists.uoregon.edu>; Tue, 5 Apr 2005 04:00:14 -0700 (PDT)
Received: from ([128.244.124.185])
	by piper.jhuapl.edu with ESMTP  id KP-BXZ33.10131903;
	Tue, 05 Apr 2005 06:59:45 -0400
In-Reply-To: <9586cbecf7e3c931aec2cec835eda5a3@isc.org>
References: <e881939938c2c4c6d84496d9ef296c46@isc.org> <Pine.LNX.4.61.0504041532270.27464@netcore.fi> <9586cbecf7e3c931aec2cec835eda5a3@isc.org>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2--899883679; protocol="application/pkcs7-signature"
Message-Id: <a8df34789f5d5bc7942fc863806c465e@innovationslab.net>
Cc: Pekka Savola <pekkas@netcore.fi>, grow@lists.uoregon.edu, ipv6@ietf.org
From: Brian Haberman <brian@innovationslab.net>
Subject: Re: grow: ipv6 anycast
Date: Tue, 5 Apr 2005 06:59:45 -0400
To: Joe Abley <jabley@isc.org>
X-Mailer: Apple Mail (2.619.2)
X-esp: ESP<8>=RBL:<0> RDNS:<0> SHA:<8> UHA:<0> SLS:<0> BAYES:<0> SPF:<0> HTML
	Dictionary (TRU6):<0> NigeriaScam Dictionary (TRU6):<0> URL
	Dictionary (TRU6):<0> Phishing:<0> Spam Dictionary (TRU6):<0>
	CAN-SPAM Compliance Dictionary (TRU6):<0> Obscenities
	Dictionary (TRU6):<0> Embed HTML Dictionary (TRU6):<0> Porn
	Dictionary (TRU6):<0> 
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk


--Apple-Mail-2--899883679
Content-Type: text/plain;
	charset=US-ASCII;
	delsp=yes;
	format=flowed
Content-Transfer-Encoding: 7bit

Hi Joe,

On Apr 4, 2005, at 22:12, Joe Abley wrote:

>
> On 4 Apr 2005, at 08:35, Pekka Savola wrote:
>
>> This is a timely topic, because IPv6 WG just less than week ago  
>> forwarded the revision of the addressing architecture to be published  
>> as Draft Standard. (IPv6 WG is Cc:ed.)
>>
>> That draft,  
>> http://www.ietf.org/internet-drafts/draft-ietf-ipv6-addr-arch-v4 
>> -02.txt still has the problematic wording wrt anycast addresses.
>
> Yes, I noticed that. I sent mail to the authors of that draft asking  
> them for their thoughts on the anycast issue, but I haven't heard  
> anything back, yet.

As a note, the current editor is only intermittently reachable due to  
personal travel.

>
> Assuming there is consensus that v6 anycast for host-based services is  
> a fait accompli, and that further prohibition is unnecessary, it would  
> seem that adjusting the relevant paragraph in the revised (v4) v6  
> addressing spec would be the cleanest way of proceeding.

My personal opinion is that the restriction should be lifted.

>
> However, although I think we had some kind of consensus to that effect  
> in the grow meeting in Minneapolis, I haven't heard any opinion from  
> those ipv6-wg folks who don't also participate in grow. Seems like  
> some kind of hum from the ipv6 floor would be useful to hear (or, if  
> no hum, active throwing of furniture).
>

I will pose that question to the group and report back.

Regards,
Brian


--Apple-Mail-2--899883679
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGJDCCAt0w
ggJGoAMCAQICAwz21DANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDQwOTAxMTcxOTM4WhcNMDUwOTAxMTcxOTM4WjBKMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMScwJQYJKoZIhvcNAQkBFhhicmlhbkBpbm5vdmF0aW9u
c2xhYi5uZXQwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDRogfqvQwSubSspmgfho1w
Br2IRBf5DI+pvLyiFcMM7KTRomseAAznLq+OjixIzT08u0opCIB91C2fohXwqf05+NVmd3/IIrOh
gQoQeFrwZdRwkmA1p6/+ivWwwyiIBBVjyIx5cdULoGi3Nl0hanW99zEHWMR7cr9YRfkhrYwyrLwF
2dUlanpDcoC+PJfimFv7Sp5Ymut3GMuvc4hrzmUBs3GhZVUbxrknxBb9C0ApLa++79wQtcrzK7Nr
HkGl63vTkfCaR2HqPE53GT1NvPSQyRUMbVBmx5xzuHUlQAY/fMDOLv45qFa9Xb8XfP1Xb+chYzHX
xPx4pqVTzZUnfi3RAgMBAAGjNTAzMCMGA1UdEQQcMBqBGGJyaWFuQGlubm92YXRpb25zbGFiLm5l
dDAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBABHGCDHcruXemZ3lBjGb0E+TXfwILkNu
UykBjSlywXfghEVSEO/cZ/0tMjrqIn1GF3GZeKecvx/aIFawl2pSUejjnLUrEE6Ro5AQs5kyZI3b
ma3GPa+TMEOeXBr8Wp+HwkMAk+McfRfGNGTDIBwF+8LnQmMCPlvTYEfuUZ93AAxCMIIDPzCCAqig
AwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4g
Q2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYG
A1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBl
cnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3
dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjELMAkGA1UEBhMCWkExJTAj
BgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJz
b25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxV
c1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuF
Wqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8
YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDag
NIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYD
VR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkq
hkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAg
k3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbq
NOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAucwggLjAgEBMGkwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMM9tQwCQYFKw4DAhoFAKCCAVMwGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDUwNDA1MTA1OTQ2WjAjBgkqhkiG9w0B
CQQxFgQUD5z4v56LM8d3seQZ2PeajvSKRvEweAYJKwYBBAGCNxAEMWswaTBiMQswCQYDVQQGEwJa
QTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3Rl
IFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAwz21DB6BgsqhkiG9w0BCRACCzFroGkwYjEL
MAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNV
BAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAgMM9tQwDQYJKoZIhvcNAQEB
BQAEggEAPdlG5TDtHiXWQmHiBqydip6R5znH/sB/SYvssjadhcaWWJUb945R7u5j8T7R0FBrG05E
0HE3pgaQCM7Hmw004vCCaPXmSMskHFnhtBpsxE+opmCAwQYFqSxAjdoJCI46ve9zhAbQUHXR1Ved
H7wZ87fkiU6Ji8KqT7ICPUBi2bXLD9smGlro1EGokKvc2LDFgM7MB4tTsDq4ecqhB2UfVZTqibkN
UnfXOxK483S7kyi1qDAOxbnfZ9JU9akH17mK4GjiVO2iltEq08YQdXZd4DqSJFtKPSM2HWf9gAZy
MFjVxTyr6deBwd4sRmbIpLY8eqnh3dqUoNMlYm4zspWPEQAAAAAAAA==

--Apple-Mail-2--899883679--

_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr  5 12:37:32 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07114
	for <grow-archive@lists.ietf.org>; Tue, 5 Apr 2005 12:37:31 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j35GUURo024844;
	Tue, 5 Apr 2005 09:30:30 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j35GUUpF024840;
	Tue, 5 Apr 2005 09:30:30 -0700 (PDT)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j35GUTbG024824
	for <grow@lists.uoregon.edu>; Tue, 5 Apr 2005 09:30:29 -0700 (PDT)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.2/8.13.2) with ESMTP id j35GUA2o012222;
	Tue, 5 Apr 2005 09:30:10 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.2/8.12.11/Submit) id j35GU8OE012221;
	Tue, 5 Apr 2005 09:30:08 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 5 Apr 2005 09:30:08 -0700
From: David Meyer <dmm@1-4-5.net>
To: Brian Haberman <brian@innovationslab.net>
Cc: Joe Abley <jabley@isc.org>, Pekka Savola <pekkas@netcore.fi>,
        grow@lists.uoregon.edu, ipv6@ietf.org
Subject: Re: grow: ipv6 anycast
Message-ID: <20050405163008.GA12200@1-4-5.net>
References: <e881939938c2c4c6d84496d9ef296c46@isc.org> <Pine.LNX.4.61.0504041532270.27464@netcore.fi> <9586cbecf7e3c931aec2cec835eda5a3@isc.org> <a8df34789f5d5bc7942fc863806c465e@innovationslab.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7"
Content-Disposition: inline
In-Reply-To: <a8df34789f5d5bc7942fc863806c465e@innovationslab.net>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader, Star Wars Episode IV.
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk


--1yeeQ81UyVL57Vl7
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 05, 2005 at 06:59:45AM -0400, Brian Haberman wrote:
> Hi Joe,
>=20
> On Apr 4, 2005, at 22:12, Joe Abley wrote:
>=20
> >
> >On 4 Apr 2005, at 08:35, Pekka Savola wrote:
> >
> >>This is a timely topic, because IPv6 WG just less than week ago =20
> >>forwarded the revision of the addressing architecture to be published =
=20
> >>as Draft Standard. (IPv6 WG is Cc:ed.)
> >>
> >>That draft, =20
> >>http://www.ietf.org/internet-drafts/draft-ietf-ipv6-addr-arch-v4=20
> >>-02.txt still has the problematic wording wrt anycast addresses.
> >
> >Yes, I noticed that. I sent mail to the authors of that draft asking =20
> >them for their thoughts on the anycast issue, but I haven't heard =20
> >anything back, yet.
>=20
> As a note, the current editor is only intermittently reachable due to =20
> personal travel.
>=20
> >
> >Assuming there is consensus that v6 anycast for host-based services is =
=20
> >a fait accompli, and that further prohibition is unnecessary, it would =
=20
> >seem that adjusting the relevant paragraph in the revised (v4) v6 =20
> >addressing spec would be the cleanest way of proceeding.
>=20
> My personal opinion is that the restriction should be lifted.

	Likewise.

> >However, although I think we had some kind of consensus to that effect =
=20
> >in the grow meeting in Minneapolis, I haven't heard any opinion from =20
> >those ipv6-wg folks who don't also participate in grow. Seems like =20
> >some kind of hum from the ipv6 floor would be useful to hear (or, if =20
> >no hum, active throwing of furniture).
> >
>=20
> I will pose that question to the group and report back.

	Thanks Brian.

	Dave


--1yeeQ81UyVL57Vl7
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCUr0QORgD1qCZ2KcRAij9AJ9ygXxWKSpvC4n4HCHZtAPIMqzFnwCcDMsh
urXdLrxm+ZStiw2hGHxez5I=
=VtBJ
-----END PGP SIGNATURE-----

--1yeeQ81UyVL57Vl7--
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From wolfman@mailAccount.com  Wed Apr  6 04:26:21 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13660;
	Wed, 6 Apr 2005 04:26:20 -0400 (EDT)
Received: from [218.152.222.34] (helo=132.151.6.1)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1DJ601-0004F6-4F; Wed, 06 Apr 2005 04:34:58 -0400
Received: from thrill-jcoppens.com (EHLO bulb.jcoppens.com) 
  by denouement.jcoppens.com with SMTP; Wed, 06 Apr 2005 11:23:14 +0200
Date: Wed, 06 Apr 2005 02:24:14 -0700
From: "Britney Stern" <wolfman@mailAccount.com>
To: gcunning@ietf.org
Cc: gency@ietf.org, geopriv@ietf.org, geopriv-admin@ietf.org,
        geopriv-web-archive@ietf.org, gga8k2ijd9ai7232@ietf.org,
        ghostsender-a.3feet.com@ietf.org, grow-archive@ietf.org, gsmp@ietf.org,
        gsmp-admin@ietf.org, gsmp-archive@ietf.org, gsmp-web-archive@ietf.org
Subject: Become a homeowner with low rates
Message-ID: <BKELLDAGKABIOCHDFD968DGAA.danny476@virgilio.it>
X-SpamTest-Info: Profile: SysLog
X-SpamTest-Status: Not detected
X-SpamTest-Version: SMTP-Filter Version 2.0.0 [542], SpamtestISP/Release
X-Mailer: MIME-tools 5.41 (Entity 5.404)
X-Spam-Score: 6.0 (++++++)
X-Spam-Flag: YES
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.3-m-n.net/sign.asp



 Best Regards,

 Brenda Flores
 
 to be remov(ed:	http://www.3-m-n.net/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From morgane@doramail.com  Wed Apr  6 04:28:55 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA13887;
	Wed, 6 Apr 2005 04:28:55 -0400 (EDT)
Received: from [211.222.191.118] (helo=132.151.6.1)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1DJ62V-0004Ji-L5; Wed, 06 Apr 2005 04:37:33 -0400
Received: from sash-jcoppens.com (EHLO feeney.jcoppens.com) 
  by essential.jcoppens.com with SMTP; Wed, 06 Apr 2005 04:24:27 -0500
Date: Wed, 06 Apr 2005 06:22:27 -0300
From: "Irene Muniz" <morgane@doramail.com>
To: gcunning@ietf.org
Cc: gency@ietf.org, geopriv@ietf.org, geopriv-admin@ietf.org,
        geopriv-web-archive@ietf.org, gga8k2ijd9ai7232@ietf.org,
        ghostsender-a.3feet.com@ietf.org, grow-archive@ietf.org, gsmp@ietf.org,
        gsmp-admin@ietf.org, gsmp-archive@ietf.org, gsmp-web-archive@ietf.org,
        haley.bledsoe@ietf.org, hive@ietf.org, hsc@ietf.org
Subject: Rates fixed 
Message-ID: <BKELLDAGKABIOCHDFD350DGAA.danny366@virgilio.it>
X-SpamTest-Info: Profile: SysLog
X-SpamTest-Status: Not detected
X-SpamTest-Version: SMTP-Filter Version 2.0.0 [494], SpamtestISP/Release
X-Mailer: MIME-tools 5.41 (Entity 5.404)
X-Spam-Score: 5.8 (+++++)
X-Spam-Flag: YES
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.3-m-n.net/sign.asp



 Best Regards,

 Carmine Blanchard
 
 to be remov(ed:	http://www.3-m-n.net/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From subgape@yebox.com  Wed Apr  6 04:37:20 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14537;
	Wed, 6 Apr 2005 04:37:18 -0400 (EDT)
Received: from [221.154.200.180] (helo=132.151.6.1)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1DJ6Aa-0004aw-F3; Wed, 06 Apr 2005 04:45:56 -0400
X-Apparently-To: gcunning@ietf.org
X-Sieve: CMU Sieve 2.2
Received: from demigod.tuple.pochta.ru ([unix socket])
         by committeewoman.reilly.pochta.ru (Cyrus v2.2.2) with LMTPA;
         Wed, 06 Apr 2005 02:33:34 -0700
Date: Wed, 06 Apr 2005 02:29:34 -0700
From: "Raymundo Jean" <subgape@yebox.com>
Message-Id: <CFE9.AA79.9A21-003002598B8C@mac.com>
X-Accept-Language: en,zh-TW,zh-CN,zh,ja,ko,tr,ru
To: gcunning@ietf.org
Cc: gency@ietf.org, geopriv@ietf.org, geopriv-admin@ietf.org,
        geopriv-web-archive@ietf.org, gga8k2ijd9ai7232@ietf.org,
        ghostsender-a.3feet.com@ietf.org, grow-archive@ietf.org, gsmp@ietf.org,
        gsmp-admin@ietf.org, gsmp-archive@ietf.org, gsmp-web-archive@ietf.org,
        haley.bledsoe@ietf.org, hive@ietf.org, hsc@ietf.org
Subject: Instant low rates
X-Mailer: Forte Agent 1.91/32.564
X-Spam-Score: 5.6 (+++++)
X-Spam-Flag: YES
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a


Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.3-m-n.net/sign.asp



 Best Regards,

 Alison Faulk
 
 to be remov(ed:	http://www.3-m-n.net/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From owner-grow@lists.uoregon.edu  Wed Apr  6 13:11:48 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06585
	for <grow-archive@lists.ietf.org>; Wed, 6 Apr 2005 13:11:48 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j36H70t2023128;
	Wed, 6 Apr 2005 10:07:00 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j36H70l9023127;
	Wed, 6 Apr 2005 10:07:00 -0700 (PDT)
Received: from felix.automagic.org (felix.hopcount.ca [204.152.186.101])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j36H6xAT023117
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <grow@lists.uoregon.edu>; Wed, 6 Apr 2005 10:06:59 -0700 (PDT)
Received: from [199.212.90.16] (helo=[199.212.90.16])
	by felix.automagic.org with esmtpsa (TLSv1:RC4-SHA:128)
	(Exim 4.42 (FreeBSD))
	id 1DJDzT-0005Ck-Aw; Wed, 06 Apr 2005 17:06:55 +0000
In-Reply-To: <E1DJC65-00079W-LC@newodin.ietf.org>
References: <E1DJC65-00079W-LC@newodin.ietf.org>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <2acad42b941e3e04dcc125df10bb6d7f@isc.org>
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org, grow@lists.uoregon.edu
From: Joe Abley <jabley@isc.org>
Subject: grow: Re: Last Call: 'IP Version 6 Addressing Architecture' to Draft Standard
Date: Wed, 6 Apr 2005 13:06:22 -0400
To: iesg@ietf.org
X-Mailer: Apple Mail (2.619.2)
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I would like to propose that the restriction on the use of anycast for 
host-based services be lifted in conjunction with the revision to the 
v6 addressing specification. Specifically, that the following text in 
section 2.6 be removed:

>    There is little experience with widespread, arbitrary use of 
> Internet
>    anycast addresses, and some known complications and hazards when
>    using them in their full generality [ANYCST].  Until more experience
>    has been gained and solutions are specified, the following
>    restrictions are imposed on IPv6 anycast addresses:
>
>       o An anycast address must not be used as the source address of an
>         IPv6 packet.
>
>       o An anycast address must not be assigned to an IPv6 host, that
>         is, it may be assigned to an IPv6 router only.

An alternative approach (updating the addressing spec using a separate 
document) can be found in draft-jabley-v6-anycast-clarify-00. To 
paraphrase that draft, there is increasing production experience with 
the use of anycast to distribute services with both IPv4 and IPv6, and 
I believe we have reached a suitable point in our experience with 
anycast that the restrictions quoted above can be lifted.

There is community support for this position, most recently expressed 
at the grow meeting Minneapolis (and in subsequent messages to the grow 
list). I have also received  private mail in support of this proposal; 
I have not yet heard anybody speak in support of retaining the text 
above. Brian Haberman tells me he will shortly raise the question on 
the ipv6 list, to gauge opinion there.

[There are many caveats for the deployment of anycast services, and the 
technique is certainly not universally applicable to all routing 
systems and all services. A treatment of the applicability and 
potential pitfalls in anycast deployment (for both v4 and v6) is in 
progress in draft-ietf-grow-anycast-00. This draft is at least another 
rev away from wglc, but such a rev could probably be made to happen 
fairly quickly if the v6 anycast position was to be clarified (e.g. in 
the interests of providing a stable normative reference for 
draft-ietf-ipv6-addr-arch-v4).]

Regards,


Joe

On 6 Apr 2005, at 11:05, The IESG wrote:

> The IESG has received a request from the IP Version 6 Working Group WG 
> to
> consider the following document:
>
> - 'IP Version 6 Addressing Architecture'
>    <draft-ietf-ipv6-addr-arch-v4-02.txt> as a Draft Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2005-04-20.
>
> The file can be obtained via
> http://www.ietf.org/internet-drafts/draft-ietf-ipv6-addr-arch-v4-02.txt
>
> Implementation Report can be accessed at
> http://www.ietf.org/IESG/implementation.html
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From rutledge@didamail.com  Thu Apr  7 14:55:26 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26746;
	Thu, 7 Apr 2005 14:55:26 -0400 (EDT)
Received: from d149-67-140-135.col.wideopenwest.com ([67.149.135.140])
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1DJcId-0006gw-5R; Thu, 07 Apr 2005 15:04:22 -0400
Received: from slaughterhouse-jcoppens.com (EHLO eject.jcoppens.com) 
  by southwest.jcoppens.com with SMTP; Thu, 07 Apr 2005 22:47:42 +0300
Date: Thu, 07 Apr 2005 21:50:42 +0200
From: "Tammi Forrest" <rutledge@didamail.com>
To: gcunning@ietf.org
Cc: gency@ietf.org, geopriv@ietf.org, geopriv-admin@ietf.org,
        geopriv-web-archive@ietf.org, gga8k2ijd9ai7232@ietf.org,
        ghostsender-a.3feet.com@ietf.org, grow-archive@ietf.org, gsmp@ietf.org,
        gsmp-admin@ietf.org
Subject: High rates? Not with us! low fixed rate
Message-ID: <BKELLDAGKABIOCHDFD116DGAA.danny166@virgilio.it>
X-SpamTest-Info: Profile: SysLog
X-SpamTest-Status: Not detected
X-SpamTest-Version: SMTP-Filter Version 2.0.0 [755], SpamtestISP/Release
X-Mailer: MIME-tools 5.41 (Entity 5.404)
X-Spam-Score: 2.5 (++)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.3-m-n.net/sign.asp



 Best Regards,

 Mary Diggs
 
 to be remov(ed:	http://www.3-m-n.net/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From dianeb@doramail.com  Thu Apr  7 20:54:55 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24553;
	Thu, 7 Apr 2005 20:54:55 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJhub-0001Tp-KT; Thu, 07 Apr 2005 21:03:54 -0400
Received: from p5481b345.dip.t-dialin.net ([84.129.179.69])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1DJhlm-0007D6-QK; Thu, 07 Apr 2005 20:54:57 -0400
Received: from paulette.recluse-bonnie.com (HELO edematous.com 66.8.150.93)
  by epithelium.com with EMQP; Thu, 07 Apr 2005 22:50:52 -0300
Date: Fri, 08 Apr 2005 03:50:52 +0200
From: "Tim Covington" <dianeb@doramail.com>
Message-Id: <CFE3.AA79.9A91dianeb@doramail.com>
To: gcunning@ietf.org
Cc: gency@ietf.org, geopriv@ietf.org, geopriv-admin@ietf.org,
        geopriv-web-archive@ietf.org, gga8k2ijd9ai7232@ietf.org,
        ghostsender-a.3feet.com@ietf.org, grow-archive@ietf.org, gsmp@ietf.org
Subject: Lowest rates in 45 years
X-Mailer: CompuServe 7.0
X-Spam-Score: 1.4 (+)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a


Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.3-m-n.net/sign.asp



 Best Regards,

 Zachery Bird
 
 to be remov(ed:	http://www.3-m-n.net/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From owner-grow@lists.uoregon.edu  Mon Apr 11 19:25:22 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11387
	for <grow-archive@lists.ietf.org>; Mon, 11 Apr 2005 19:25:16 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3BNLt7H014040;
	Mon, 11 Apr 2005 16:21:56 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3BNLtFh014038;
	Mon, 11 Apr 2005 16:21:55 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3BH2KK9014023
	for <grow@lists.uoregon.edu>; Mon, 11 Apr 2005 10:02:20 -0700 (PDT)
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-2.cisco.com with ESMTP; 11 Apr 2005 10:02:05 -0700
Received: from cisco.com (vaf-lnx1.cisco.com [171.71.140.59])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j3BH21ZV023568
	for <grow@lists.uoregon.edu>; Mon, 11 Apr 2005 10:02:02 -0700 (PDT)
Received: from vaf-lnx1.cisco.com (vaf-lnx1 [127.0.0.1])
	by cisco.com (8.12.11/8.12.11) with ESMTP id j3BH21jb012367
	for <grow@lists.uoregon.edu>; Mon, 11 Apr 2005 10:02:01 -0700
Received: (from vaf@localhost)
	by vaf-lnx1.cisco.com (8.12.11/8.12.11/Submit) id j3BH20cj012365
	for grow@lists.uoregon.edu; Mon, 11 Apr 2005 10:02:00 -0700
X-Authentication-Warning: vaf-lnx1.cisco.com: vaf set sender to vaf@cisco.com using -f
Date: Mon, 11 Apr 2005 10:02:00 -0700
From: Vince Fuller <vaf@cisco.com>
To: grow@lists.uoregon.edu
Subject: grow: draft of new RFC1519 replacement
Message-ID: <20050411170200.GA11870@vaf-lnx1.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

As part of the NEWTRK effort, the CIDR document (RFC1519) is being updated.

What follows is a current draft of the new document. At this point, it is
not clear whether this will become a GROW WG draft but the authors would
appreciate review and comments from the members of this list.

	Thanks,
	Vince and Tony

		--------------------

Network Working Group                                          V. Fuller
Internet-Draft                                                     T. Li
Expires: October 10, 2005                                  Cisco Systems
                                                           April 8, 2005


 Classless Inter-Domain Routing (CIDR): The Internet Address Assignment
                          and Aggregation Plan
                        draft-vaf-cidrupdate-00

Status of this Memo

   This document is an Internet-Draft and is subject to all provisions
   of Section 3 of RFC 3667.  By submitting this Internet-Draft, each
   author represents that any applicable patent or other IPR claims of
   which he or she is aware have been or will be disclosed, and any of
   which he or she become aware will be disclosed, in accordance with
   RFC 3668.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on October 10, 2005.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This memo discusses the strategy for address assignment of the
   existing 32-bit IPv4 address space with a view toward conserving the
   address space and limiting the growth rate of global routing state.
   This document is intended as a replacement to the original CIDR spec
   [RFC1519] with changes made both to clarify the concepts it



Fuller & Li             Expires October 10, 2005                [Page 1]

Internet-Draft            CIDR Address Strategy               April 2005


   introduced and, after more than twelve years, to update the Internet
   community on the results of deploying the technology it described.

Table of Contents

   1.   History and Problem Description  . . . . . . . . . . . . . .   3
   2.   Classless addressing as a solution . . . . . . . . . . . . .   4
     2.1  Basic concept and prefix notation  . . . . . . . . . . . .   5
   3.   Address assignment and routing aggregation . . . . . . . . .   7
     3.1  Aggregation efficiency and limitations . . . . . . . . . .   7
     3.2  Distributed assignment of address space  . . . . . . . . .   9
   4.   Routing implementation considerations  . . . . . . . . . . .  10
     4.1  Rules for route advertisement  . . . . . . . . . . . . . .  10
     4.2  How the rules work . . . . . . . . . . . . . . . . . . . .  11
     4.3  A note on prefix filter formats  . . . . . . . . . . . . .  12
     4.4  Responsibility for and configuration of aggregation  . . .  12
     4.5  Route propagation and routing protocol considerations  . .  14
   5.   Example of new address assignments and routing . . . . . . .  14
     5.1  Address delegation . . . . . . . . . . . . . . . . . . . .  14
     5.2  Routing advertisements . . . . . . . . . . . . . . . . . .  16
   6.   Domain Name Service considerations . . . . . . . . . . . . .  17
   7.   Transition to a long term solution . . . . . . . . . . . . .  19
   8.   Analysis of CIDR's effect on global routing state  . . . . .  19
   9.   Conclusions and Recommendations  . . . . . . . . . . . . . .  21
   10.  Security Considerations  . . . . . . . . . . . . . . . . . .  21
   11.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . .  23
   12.  References . . . . . . . . . . . . . . . . . . . . . . . . .  23
     12.1   Normative References . . . . . . . . . . . . . . . . . .  23
     12.2   Informative References . . . . . . . . . . . . . . . . .  23
        Authors' Addresses . . . . . . . . . . . . . . . . . . . . .  25
        Intellectual Property and Copyright Statements . . . . . . .  26




















Fuller & Li             Expires October 10, 2005                [Page 2]

Internet-Draft            CIDR Address Strategy               April 2005


1.  History and Problem Description

   What is now known as the Internet started as a research project in
   the 1970s to design and develop a set of protocols that could be used
   with many different network technologies to provide a seamless, end-
   to-end facility for interconnecting a diverse set of end systems.
   When determining how the 32-bit address space would be used, certain
   assumptions were made about the number of organizations to be
   connected, the number of end systems per organization, and total
   number of end systems on the network.  The end result was the
   establishment (see [RFC791]) of three classes  of networks: class A
   (most significant address bits '00'), with 128 possible networks each
   with 16777216 end systems (minus special bit values reserved for
   network/broadcast addresses); class B (MSB '10'), with 16384 possible
   networks each with 65536 end systems (less reserved values); and
   class C (MSB '110'), with 2097152 possible networks each with 254 end
   systems (256 bit combinations minus the reserved all-zeros and all-
   ones patterns).  The set of addresses with MSB '111' was reserved for
   future use; parts of this were eventually defined (MSB '1110') for
   use with IPv4 multicast and parts are still reserved as of the
   writing of this document.

   In the late 1980s, the expansion and commercialization of the former
   research network resulted in the connection of many new organizations
   to the rapidly-growing Internet and each new organization required an
   address assignment according to the class A/B/C addressing plan.  As
   demand for new network numbers, particularly in the class B space
   started to take on what appeared to be an exponential growth rate,
   some members of the operations and engineering community started to
   have concerns over the long-term scaling properties of the class
   A/B/C system and began thinking about how to modify network number
   assignment policy and routing protocols to better accommodate the
   growth.  In November, 1991, the IETF created the ROAD (Routing and
   Addressing) group to examine the situation.  This group met in
   January, 1992 and identified three major problems:

   1.  Exhaustion of the class B network address space.  One fundamental
       cause of this problem is the lack of a network class of a size
       which is appropriate for mid-sized organization; class C, with a
       maximum of 254 host addresses, is too small, while class B, which
       allows up to 65534 host addresses, is too large for most
       organizations but was the best fit available for use with
       subnetting.

   2.  Growth of routing tables in Internet routers beyond the ability
       of current software, hardware, and people to effectively manage.





Fuller & Li             Expires October 10, 2005                [Page 3]

Internet-Draft            CIDR Address Strategy               April 2005


   3.  Eventual exhaustion of the 32-bit IPv4 address space.

   It was clear that then-current rates of Internet growth would cause
   the first two problems to become critical some time between 1993 and
   1995.  Work already in progress on topological assignment of
   addressing for CLNS, which was presented to the community at the
   Boulder IETF in December of 1990, led to thoughts on how to re-
   structure the 32-bit IPv4 address space to increase its lifespan.
   Work in the ROAD group followed and eventually resulted in the
   publication of [RFC1338] and later [RFC1519].

   The design and deployment of CIDR was intended to solve these
   problems by providing a mechanism to slow the growth of global
   routing tables and to reduce the rate of consumption of IPv4 address
   space.  It did not and does not attempt to solve the third problem,
   which is of a more long-term nature, but instead endeavors to ease
   enough of the short to mid-term difficulties to allow the Internet to
   continue to function efficiently while progress is made on a longer-
   term solution.

   More historical background on this effort and on the ROAD group may
   be found in [RFC1380] and at [LWRD].

2.  Classless addressing as a solution

   The solution that the community created was to deprecate the Class
   A/B/C network address assignment system in favor of using
   "classless", hierarchical blocks of IP addresses (referred to as
   prefixes).  The assignment of prefixes is intended to roughly follow
   the underlying Internet topology so that aggregation can be used to
   facilitate scaling of the global routing system.  One implication of
   this strategy is that prefix assignment and aggregation is generally
   done according to provider-subscriber relationships, since that is
   how the Internet topology is determined.

   When originally proposed in [RFC1338] and [RFC1519], this addressing
   plan was intended to be a relatively short-term response, lasting
   approximately three to five years during which a more permanent
   addressing and routing architecture would be designed and
   implemented.  As can be inferred from the dates on the original
   documents, CIDR has far outlasted its anticipated lifespan and has
   become the mid-term solution to the problems described above.

   Coupled with address management strategies implemented by the
   Regional Internet Registries (see [NRO] for details), the deployment
   of CIDR-style addressing has also reduced the rate at which IPv4
   address space has been consumed, thus providing short-to-medium-term
   relief to problem #3 described above.



Fuller & Li             Expires October 10, 2005                [Page 4]

Internet-Draft            CIDR Address Strategy               April 2005


   Note that, as defined, this plan neither requires nor assumes the re-
   assignment of those parts of the legacy "class C" space that are not
   amenable to aggregation (sometimes called "the swamp").  Doing so
   would somewhat reduce routing table sizes (current estimate is that
   "the swamp" contains approximately 15,000 entries) though at a
   significant renumbering cost.  Similarly, there is no hard
   requirement that any end site renumber when changing transit service
   provider but end sites are encouraged do so to eliminate the need for
   explicit advertisement of their prefixes into the global routing
   system.

2.1  Basic concept and prefix notation

   In the simplest sense, the change from Class A/B/C network numbers to
   classless prefixes is to make explicit which bits in a 32-bit IPv4
   address are interpreted as the network number (or prefix) associated
   with a site and which are the used to number individual end systems
   within the site.  In CIDR notation, a prefix is shown as a 4-octet
   quantity, just like a traditional IPv4 address or network number,
   followed by the "/" (slash) character, followed by a decimal value
   between 0 and 32 that describes the number of significant bits.

   For example, the legacy "class B" network 172.16.0.0, with an implied
   network mask of 255.255.0.0, is defined as the prefix 172.16.0.0/16,
   the "/16" indicating that the mask to extract the network portion of
   the prefix is a 32-bit value where the most significant 16 bits are
   ones and the least significant 16 bits are zeros.  Similarly, the
   legacy "class C" network number 192.168.99.0 is defined as the prefix
   192.168.99.0/24 - the most significant 24 bits are ones and the least
   significant 8 bits are zeros.

   Using classless prefixes with explicit prefix lengths allows much
   more flexible matching of address space blocks to actual need.  Where
   formerly only three network sizes were available, prefixes may be
   defined to describe any power-of-two-sized block of between one and
   2^32 end system addresses.  In practice, the unallocated pool of
   addresses is administered by the Internet Assigned Numbers Authority
   ([IANA]).  The IANA makes allocations from this pool to Regional
   Internet Registries, as required.  These allocations are made in
   contiguous bit-aligned blocks of 2^24 addresses (a.k.a. /8 prefixes).
   The RIRs, in turn, allocate or assign smaller address blocks to Local
   Internet Registries (LIRs) or Internet Service Providers (ISPs).
   These entities may make direct use of the assignment (as would
   commonly be the case for an ISP) or may make further sub-allocations
   of addresses to their customers.  These RIR address assignments vary
   according to the needs of each ISP or LIR.  For example, a large ISP
   might be allocated an address block of 2^17 addresses (a /15 prefix)
   while a smaller ISP may be allocated an address block of 2^11



Fuller & Li             Expires October 10, 2005                [Page 5]

Internet-Draft            CIDR Address Strategy               April 2005


   addresses (a /21 prefix).

   Note that the terms "allocate" and "assign" have specific meaning in
   the Internet address registry system; "allocate" refers to the
   delegation of a block of address space to an organization which is
   expected to perform further sub-delegations while "assign" is used
   for sites that directly use (i.e. number individual hosts) the block
   of addresses received.

   The following table provides a convenient short-cut to all of the
   CIDR prefix sizes, showing the number of addresses possible in each
   prefix and the number of prefixes of that size that may be numbered
   in the 32-bit IPv4 address space:


       notation       addrs/block      # blocks
       --------       -----------     ----------
       n.n.n.n/32               1     4294967296    "host route"
       n.n.n.x/31               2     2147483648    "[RFC3021] p2p link"
       n.n.n.x/30               4     1073741824
       n.n.n.x/29               8      536870912
       n.n.n.x/28              16      268435456
       n.n.n.x/27              32      134217728
       n.n.n.x/26              64       67108864
       n.n.n.x/25             128       33554432
       n.n.n.0/24             256       16777216    legacy "class C"
       n.n.x.0/23             512        8388608
       n.n.x.0/22            1024        4194304
       n.n.x.0/21            2048        2097152
       n.n.x.0/20            4096        1048576
       n.n.x.0/19            8192         524288
       n.n.x.0/18           16384         262144
       n.n.x.0/17           32768         131072
       n.n.0.0/16           65536          65536    legacy "class B"
       n.x.0.0/15          131072          32768
       n.x.0.0/14          262144          16384
       n.x.0.0/13          524288           8192
       n.x.0.0/12         1048576           4096
       n.x.0.0/11         2097152           2048
       n.x.0.0/10         4194304           1024
       n.x.0.0/9          8388608            512
       n.0.0.0/8         16777216            256    legacy "class A"
       x.0.0.0/7         33554432            128
       x.0.0.0/6         67108864             64
       x.0.0.0/5        134217728             32
       x.0.0.0/4        268435456             16
       x.0.0.0/3        536870912              8
       x.0.0.0/2       1073741824              4



Fuller & Li             Expires October 10, 2005                [Page 6]

Internet-Draft            CIDR Address Strategy               April 2005


       x.0.0.0/1       2147483648              2
       0.0.0.0/0       4294967296              1    "default route"

   n is an 8-bit, decimal octet value.

   x is a 1 to 7 bit value, base on the prefix length, shifted into the
   most significant bits of the octet and converted into decimal form;
   the least significant bits of the octet are zero.

   In practice, prefixes of length shorter than 8 are not allocated or
   assigned though routes to such short prefixes may exist in routing
   tables if or when aggressive aggregation is performed.  As of the
   writing of this document, no such routes are seen in the global
   routing system but operator error and other events have caused some
   of them (i.e. 128.0.0.0/1 and 192.0.0.0/2) to be observed in some
   networks at some times in the past.

3.  Address assignment and routing aggregation

   Classless addressing and routing was initially developed primarily to
   improve the scaling properties of routing on the global Internet.
   Because the scaling of routing is very tightly coupled to the way
   that addresses are used, deployment of CIDR had implications for the
   way in which addresses were assigned.

3.1  Aggregation efficiency and limitations

   The only commonly-understood method for reducing routing state on a
   packet-switched network is through aggregation of information.  For
   CIDR to succeed in reducing the size and growth rate of the global
   routing system, the IPv4 address assignment process needed to be
   changed to make possible the aggregation of routing information along
   topological lines.  Since, in general, the topology of the network is
   determined by the service providers who have built it, topologically-
   significant address assignments are necessarily service-provider
   oriented.

   Aggregation is simple for an end site which is connected to one
   service provider: it uses address space assigned by its service
   provider and that address space is a small piece of a larger block
   allocated to the service provider.  No explicit route is needed for
   the end site - the service provider advertises a single aggregate
   route for the larger block; this advertisement provides reachability
   and routeability for all of the customers numbered in the block.

   There are two, more complex, situations that reduce the effectiveness
   of aggregation:




Fuller & Li             Expires October 10, 2005                [Page 7]

Internet-Draft            CIDR Address Strategy               April 2005


   o  An organization which is multi-homed.  Because a multi-homed
      organization must be advertised into the system by each of its
      service providers, it is often not feasible to aggregate its
      routing information into the address space of any one of those
      providers.  Note that the organization still may receive its
      address assignment out of a service provider's address space
      (which has other advantages), but a route to the organization's
      prefix must still be explicitly advertised by all of its service
      providers.  For this reason, the global routing cost for a multi-
      homed organization is generally the same as it was prior to the
      adoption of CIDR.

   o  An organization which changes service provider but does not
      renumber.  This has the effect of "punching a hole" in one of the
      original service provider's aggregated route advertisements.  CIDR
      handles this situation by requiring the newer service provider to
      advertise a specific advertisement for the re-homed organization;
      this advertisement is preferred over provider aggregates because
      it is a longer match.  To maintain efficiency of aggregation, it
      is recommended that an organization which changes service
      providers plan to eventually migrate its network into a an prefix
      assigned from its new provider's address space.  To this end, it
      is recommended that mechanisms to facilitate such migration, such
      as dynamic host address assignment using [RFC2131]) be deployed
      wherever possible, and that additional protocol work be done to
      develop improved technology for renumbering.

   Note that some aggregation efficiency gain can still be had for
   multi-homed sites (and, in general, for any site composed of
   multiple, logical IPv4 networks) - by allocating a contiguous power-
   of-two block address space to the site (as opposed to multiple,
   independent prefixes) the site's routing information may be
   aggregated into a single prefix.  Also, since the routing cost
   associated with assigning a multi-homed site out of a service
   provider's address space is no greater than the old method of
   sequential number assignment by a central authority, it makes sense
   to assign all end-site address space out of blocks allocated to
   service providers.

   It is also worthwhile to mention that since aggregation may occur at
   multiple levels in the system, it may still be possible to aggregate
   these anomalous routes at higher levels of whatever hierarchy may be
   present.  For example, if a site is multi-homed to two relatively
   small providers that both obtain connectivity and address space from
   the same large provider, then aggregation by the large provider of
   routes from the smaller networks will include all routes to the
   multi-homed site.  The feasibility of this sort of second-level
   aggregation depends on whether topological hierarchy exists between a



Fuller & Li             Expires October 10, 2005                [Page 8]

Internet-Draft            CIDR Address Strategy               April 2005


   site, its directly-connected providers, and other providers to which
   they are connected; it may be practical in some regions of the global
   Internet but not in others.

   Note: in the discussion and examples which follow, prefix notation is
   used to represent routing destinations.  This is used for
   illustration only and does not require that routing protocols use
   this representation in their updates.

3.2  Distributed assignment of address space

   In the early days of the Internet, IPv4 address space assignment was
   performed by the central Network Information Center (NIC).  Class
   A/B/C network numbers were assigned in essentially arbitrary order,
   roughly according to the size of the organizations that requested
   them.  All assignments were recorded centrally and no attempt was
   made to assign network numbers in a manner that would allow routing
   aggregation.

   When CIDR was originally deployed, the central assignment authority
   continued to exist but changed its procedures to assign large blocks
   of "Class C" network numbers to each service provider.  Each service
   provider, in turn, assigned bitmask-oriented subsets of the
   provider's address space to each customer.  This worked reasonably
   well as long as the number of service providers was relatively small
   and relatively constant but did not scale well as the number of
   service providers grew at a rapid rate.

   As the Internet started to expand rapidly in the 1990s, it became
   clear that a single, centralized address assignment authority was
   problematic.  This function began being de-centralized when address
   space assignment for European Internet sites was delegated in bit-
   aligned blocks of 16777216 addresses (what CIDR would later define as
   a /8) to the RIPE NCC ([RIPE]), effectively making it the first of
   the RIRs.  Since then, address assignment has been formally
   distributed as a hierarchical function with IANA, the RIRs, and the
   service providers.  Removing the bottleneck of a single organization
   having responsibility for the global Internet address space greatly
   improved the efficiency and response time for new assignments.

   Hierarchical delegation of addresses in this manner implies that
   sites with addresses assigned out of a given service provider are,
   for routing purposes, part of that service provider and will be
   routed via its infrastructure.  This implies that routing information
   about multi-homed organizations, i.e., organizations connected to
   more than one network service provider, will still need to be known
   by higher levels in the hierarchy.




Fuller & Li             Expires October 10, 2005                [Page 9]

Internet-Draft            CIDR Address Strategy               April 2005


   Some of these issues are discussed at greater length in [RFC1518].

4.  Routing implementation considerations

   With the change from classful network numbers to classless prefixes,
   it is not possible to infer the network mask from the initial bit
   pattern of an IPv4 address.  This has implications for how routing
   information is stored and propagated.  Network masks or prefix
   lengths must be explicitly carried in routing protocols.  Interior
   routing protocols such as OSPF [RFC2178], IS-IS [RFC1195], RIPv2
   [RFC2453], and Cisco EIGRP, and the BGP4 exterior routing protocol
   [RFC1771] all support this functionality, having been developed or
   modified as part of the deployment of classless inter-domain routing
   during the 1990s.

   Older interior routing protocols, such as RIP [RFC1058], HELLO, and
   Cisco IGRP, and older exterior routing protocols, such as EGP
   [RFC904], do not support explicit carriage of prefix length/mask and
   thus cannot be effectively used on the Internet in other than very
   limited, stub configurations.  While their use may be appropriate in
   simple, legacy end-site configurations, they are considered obsolete
   and should NOT be used in transit networks connected to the global
   Internet.

   Similarly, routing and forwarding tables in layer-3 network equipment
   must be organized to store both prefix and prefix length or mask.
   Equipment which organizes its routing/forwarding information
   according to legacy class A/B/C network/subnet conventions cannot be
   expected to work correctly on networks connected to the global
   Internet; use of such equipment is not recommended.  Fortunately,
   very little such equipment is in use today.

4.1  Rules for route advertisement

   1.  Routing to all destinations must be done on a longest-match basis
       only.  This implies that destinations which are multi-homed
       relative to a routing domain must always be explicitly announced
       into that routing domain - they cannot be summarized (this makes
       intuitive sense - if a network is multi-homed, all of its paths
       into a routing domain which is "higher" in the hierarchy of
       networks must be known to the "higher" network).

   2.  A router which generates an aggregate route for multiple, more-
       specific routes must discard packets which match the aggregate
       route but not any of the more-specific routes.  In other words,
       the "next hop" for the aggregate route should be the null
       destination.  This is necessary to prevent forwarding loops when
       some addresses covered by the aggregate are not reachable.



Fuller & Li             Expires October 10, 2005               [Page 10]

Internet-Draft            CIDR Address Strategy               April 2005


   Note that during failures, partial routing of traffic to a site which
   takes its address space from one service provider but which is
   actually reachable only through another (i.e., the case of a site
   which has changed service providers) may occur because such traffic
   will be forwarded along the path advertised by the aggregated route.
   Rule #2 will prevent packet mis-delivery by causing such traffic to
   be discarded by the advertiser of the aggregated route, but the
   output of "traceroute" and other similar tools will suggest that a
   problem exists within that network rather than in the network which
   is no longer advertising the more-specific prefix.  This may be
   confusing to those trying to diagnose connectivity problems; see the
   example in Section 5.2 for details.  A solution to this perceived
   "problem" is beyond the scope of this document - it lies with better
   education of the user/operator community, not in routing technology.

   An implementation following these rules should also be generalized,
   so that an arbitrary network number and mask are accepted for all
   routing destinations.  The only outstanding constraint is that the
   mask must be left contiguous.  Note that the degenerate route to
   prefix 0.0.0.0/0 is used as a default route and MUST be accepted by
   all implementations.  Further, to protect against accidental
   advertisements of this route via the inter-domain protocol, this
   route should only be advertised when a router is explicitly
   configured to do so - never as a non-configured, "default" option.

4.2  How the rules work

   Rule #1 guarantees that the routing algorithm used is consistent
   across implementations and consistent with other routing protocols,
   such as OSPF.  Multi-homed networks are always explicitly advertised
   by every service provider through which they are routed even if they
   are a specific subset of one service provider's aggregate (if they
   are not, they clearly must be explicitly advertised).  It may seem as
   if the "primary" service provider could advertise the multi-homed
   site implicitly as part of its aggregate, but the assumption that
   longest-match routing is always done causes this not to work.

   Rule #2 guarantees that no routing loops form due to aggregation.
   Consider a site that has been assigned 192.168.64/19 by its "parent"
   provider that has 192.168.0.0/16.  The "parent" network will
   advertise 192.168.0.0/16 to the "child" network.  If the "child"
   network were to lose internal connectivity to 192.168.65.0/24 (which
   is part of its aggregate), traffic from the "parent" to the to the
   "child" destined for 192.168.65.1 will follow the "child's"
   advertised route.  When that traffic gets to the "child", however,
   the mid-level *must not* follow the route 192.168.0.0/16 back up to
   the "parent", since that would result in a forwarding loop.  Rule #2
   says that the "child" may not follow a less-specific route for a



Fuller & Li             Expires October 10, 2005               [Page 11]

Internet-Draft            CIDR Address Strategy               April 2005


   destination which matches one of its own aggregated routes
   (typically, this is implemented by installing a "discard" or "null"
   route for all aggregated prefixes which one network advertises to
   another).  Note that handling of the "default" route (0.0.0.0/0) is a
   special case of this rule - a network must not follow the default to
   destinations which are part of one of it's aggregated advertisements.

4.3  A note on prefix filter formats

   Systems which process route announcements must be able to verify that
   information which they receive is acceptable according to policy
   rules.  Implementations which filter route advertisements must allow
   masks or prefix lengths in filter elements.  Thus, filter elements
   which formerly were specified as:

           accept 172.16.0.0
           accept 172.25.120.0.0
           accept 172.31.0.0
           deny 10.2.0.0
           accept 10.0.0.0

   now look something like:

           accept 172.16.0.0/16
           accept 172.25.0.0/16
           accept 172.31.0.0/16
           deny 10.2.0.0/16
           accept 10.0.0.0/8

   This is merely making explicit the network mask which was implied by
   the class A/B/C classification of network numbers.  It is also useful
   to enhance filtering capability to allow the match of a prefix and
   all more-specific prefixes with the same bit pattern; fortunately,
   this functionality has been implemented by most vendors of equipment
   used on the Internet.

4.4  Responsibility for and configuration of aggregation

   Under normal circumstances, a routing domain (or "Autonomous System")
   which has been allocated or assigned a set of prefixes has sole
   responsibility for aggregation of those prefixes.  In the usual case,
   the AS will install configuration in one or more of its routers to
   generate aggregate routes based on more-specific routes known to its
   internal routing system; these aggregate routes are advertised into
   the global routing system by the border routers for the routing
   domain.  The more-specific internal routes which overlap with the
   aggregate routes should not be advertised globally.  In some cases,
   an AS may wish to delegate aggregation responsibility to another AS



Fuller & Li             Expires October 10, 2005               [Page 12]

Internet-Draft            CIDR Address Strategy               April 2005


   (for example, a customer may wish for its service provider to
   generate aggregated routing information on its behalf); in such
   cases, aggregation is performed by a router in the second AS based on
   the routes that it receives from the first combined with configured
   policy information describing how those routes should be aggregated.

   It should be mentioned that one provider may choose to perform
   aggregation on the routes it receives from another without explicit
   agreement; this is termed "proxy aggregation".  This can be a useful
   tool for reducing the amount of routing state that an AS must carry
   and propagate to its customers and neighbors, proxy aggregation can
   also create inconsistencies in global routing state.  Consider what
   happens if both AS 2 and 3 receive routes from AS 1 but AS 2 performs
   proxy aggregation while AS 3 does not.  Other AS's which receive
   transit routing information from both AS 2 and AS 3 will see an
   inconsistent view of the routing information originated by AS 1.
   This may cause an unexpected shift of traffic toward AS 1 through AS
   3 for AS 3's customers and any others receiving transit routes from
   AS 3.  Because proxy aggregation can cause unanticipated consequences
   for parts of the Internet that have no relationship with either the
   source of the aggregated routes or the party providing aggregation,
   it should be used with extreme caution.

   Configuration of the routes to be combined into aggregates is an
   implementation of routing policy and does require some manually-
   maintained information.  As an addition to the information that must
   be maintained for a set of routeable prefixes, aggregation
   configuration is typically just a line or two defining the range of
   the block of IPv4 addresses to aggregate.  A site performing its own
   aggregation is doing so for address blocks that it has been assigned;
   a site performing aggregation on behalf of another knows this
   information based on an agreement to delegate aggregation.  Assuming
   a best common practice for network administrators to exchange lists
   of prefixes to accept from one and other, configuration of
   aggregation information does not introduce significant additional
   administrative overhead.

   The generation of an aggregate route is usually specified either
   statically or in response to learning an active dynamic route for a
   prefix contained within the aggregate route.  If such dynamic
   aggregate route advertisement is done, care should be taken that
   routes are not excessively added or withdrawn (known as "route
   flapping"); in general, a dynamic aggregate route advertisement is
   added when at least one component of the aggregate becomes reachable
   and it is withdrawn only when all components become unreachable.
   Properly configured, aggregated routes are more stable than non-
   aggregated routes and thus improve global routing stability.




Fuller & Li             Expires October 10, 2005               [Page 13]

Internet-Draft            CIDR Address Strategy               April 2005


   Implementation note: aggregation of the "Class D" (multicast) address
   space is beyond the scope of this document.

4.5  Route propagation and routing protocol considerations

   Prior to the original deployment of CIDR, common practice was to
   propagate routes learned via exterior routing protocols (i.e.  EGP or
   BGP) through a site's interior routing protocol (typically, OSPF,
   IS-IS, or RIP).  This was done to ensure that consistent and correct
   exit points were chosen for traffic destined to a destination learned
   through those protocols.  Four evolutionary effects -- the advent of
   CIDR, explosive growth of global routing state, widespread adoption
   of BGP4, and a requirement to propagate full path information -- have
   combined to deprecate that practice.  To ensure proper path
   propagation and prevent inter-AS routing inconsistency (BGP4's loop
   detection/prevention mechanism requires full path propagation),
   transit networks must use internal BGP (iBGP) for carrying routes
   learned from other providers both within and through their networks.

5.  Example of new address assignments and routing

5.1  Address delegation

   Consider the block of 524288 (2^19) addresses beginning with
   10.24.0.0 and ending with 10.31.255.255 allocated to a single network
   provider, "PA".  This is equivalent in size to a block of 2048 legacy
   "class C" network numbers (or /24s).  A classless route to this block
   would be described as 10.24.0.0 with mask of 255.248.0.0 the prefix
   10.24.0.0/13.

   Assume this service provider connects six sites in the following
   order (significant because it demonstrates how temporary "holes" may
   form in the service provider's address space):

   o  "C1" requiring fewer than 2048 addresses (/21 or 8 x /24)

   o  "C2" requiring fewer than 4096 addresses (/20 or 16 x /24)

   o  "C3" requiring fewer than 1024 addresses (/22 or 4 x /24)

   o  "C4" requiring fewer than 1024 addresses (/22 or 4 x /24)

   o  "C5" requiring fewer than 512 addresses (/23 or 2 x /24)

   o  "C6" requiring fewer than 512 addresses (/23 or 2 x /24)

   In all cases, the number of IPv4 addresses "required" by each site is
   assumed to allow for significant growth.  The service provider



Fuller & Li             Expires October 10, 2005               [Page 14]

Internet-Draft            CIDR Address Strategy               April 2005


   delegates its address space as follows:

   o  C1: assign 10.24.0 through 10.24.7.  This block of networks is
      described by the route 10.24.0.0/21 (mask 255.255.248.0)

   o  C2: assign 10.24.16 through 10.24.31.  This block is described by
      the route 10.24.16.0/20 (mask 255.255.240.0)

   o  C3: assign 10.24.8 through 10.24.11.  This block is described by
      the route 10.24.8.0/22 (mask 255.255.252.0)

   o  C4: assign 10.24.12 through 10.24.15.  This block is described by
      the route 10.24.12.0/22 (mask 255.255.252.0)

   o  C5: assign 10.24.32 and 10.24.33.  This block is described by the
      route 10.24.32.0/23 (mask 255.255.254.0)

   o  C6: assign 10.24.34 and 10.24.35.  This block is described by the
      route 10.24.34.0/23 (mask 255.255.254.0)

   These six sites should be represented as six prefixes of varying size
   within the provider IGP.  If, for some reason, the provider were to
   use an obsolete IGP that doesn't support classless routing or
   variable-length subnets, then then explicit routes all /24s will have
   to be carried.

   To make this example more realistic, assume that C4 and C5 are multi-
   homed through some other service provider, "PB".  Further assume the
   existence of a site "C7" which was originally connected to "RB" but
   has moved to "PA".  For this reason, it has a block of network
   numbers which are assigned out "PB"'s block of (the next) 2048 x /24.

   o  C7: assign 10.32.0 through 10.32.15.  This block is described by
      the route 10.32.0.0/20 (mask 255.255.240.0)

   For the multi-homed sites, assume that C4 is advertised as primary
   via "RA" and secondary via "RB"; C5 is primary via "RB" and secondary
   via "RA".  In addition, assume that "RA" and "RB" are both connected
   to the same transit service provider "BB".

   Graphically, this topology looks something like this:










Fuller & Li             Expires October 10, 2005               [Page 15]

Internet-Draft            CIDR Address Strategy               April 2005


   10.24.0.0 -- 10.24.7.0__         __10.32.0.0 - 10.32.15.0
   C1: 10.24.0.0/21        \       /  C7: 10.32.0.0/20
                            \     /
                             +----+                              +----+
   10.24.16.0 - 10.24.31.0_  |    |                              |    |
   C2: 10.24.16.0/20       \ |    |  _10.24.12.0 - 10.24.15.0__  |    |
                            \|    | / C4: 10.24.12.0/20        \ |    |
                             |    |/                            \|    |
   10.24.8.0 - 10.24.11.0___/| PA |\                             | PB |
   C3: 10.24.8.0/22          |    | \__10.24.32.0 - 10.24.33.0___|    |
                             |    |    C5: 10.24.32.0/23         |    |
                             |    |                              |    |
   10.24.34.0 - 10.24.35.0__/|    |                              |    |
   C6: 10.24.34.0/23         |    |                              |    |
                             +----+                              +----+
                               ||                                  ||
   routing advertisements:     ||                                  ||
                               ||                                  ||
           10.24.12.0/22 (C4)  ||              10.24.12.0/22 (C4)  ||
           10.32.0.0/20 (C7)   ||              10.24.32.0/23 (C5)  ||
           10.24.0.0/13 (PA)   ||              10.32.0.0/13 (PB)   ||
                               ||                                  ||
                               VV                                  VV
                            +---------- BACKBONE NETWORK BB ----------+


5.2  Routing advertisements

   To follow rule #1, PA will need to advertise the block of addresses
   that it was given and C7.  Since C4 is multi-homed and primary
   through PA, it must also be advertised.  C5 is multi-homed and
   primary through PB.  In principal (and in the example above), it need
   not be advertised since longest match by PB will automatically select
   PB as primary and the advertisement of PA's aggregate will be used as
   a secondary.  In actual practice, C5 will normally be advertised via
   both providers.

   Advertisements from "PA" to "BB" will be:

          10.24.12.0/22 primary    (advertises C4)
          10.32.0.0/20 primary     (advertises C7)
          10.24.0.0/13 primary     (advertises remainder of PA)

   For PB, the advertisements must also include C4 and C5 as well as
   it's block of addresses.

   Advertisements from "PB" to "BB" will be:




Fuller & Li             Expires October 10, 2005               [Page 16]

Internet-Draft            CIDR Address Strategy               April 2005


          10.24.12.0/22 secondary  (advertises C4)
          10.24.32.0/23 primary    (advertises C5)
          10.32.0.0/13 primary     (advertises remainder of RB)

   To illustrate the problem diagnosis issue mentioned in Section 4.1,
   consider what happens if PA loses connectivity to C7 (the site which
   is assigned out of PB's space).  In a stateful protocol, PA will
   announce to BB that 10.32.0.0/20 has become unreachable.  Now, when
   BB flushes this information out of its routing table, any future
   traffic sent through it for this destination will be forwarded to PB
   (where it will be dropped according to Rule #2) by virtue of PB's
   less specific match 10.32.0.0/13.  While this does not cause an
   operational problem (C7 is unreachable in any case), it does create
   some extra traffic across "BB" (and may also prove confusing to
   someone trying to debug the outage with "traceroute").  A mechanism
   to cache such unreachable state might be nice but is beyond the scope
   of this document.

6.  Domain Name Service considerations

   One aspect of Internet services which was notably affected by the
   move to CIDR was the mechanism used for address-to-name translation:
   the IN-ADDR.ARPA zone of the domain system.  Because this zone is
   delegated on octet boundaries only, the move to an address assignment
   plan which uses bitmask-oriented addressing caused some increase in
   work for those who maintain parts of the IN-ADDR.ARPA zone.

   As described above, the IN-ADDR.ARPA zone is necessarily organized
   along octet boundaries.  Prior to the adoption of CIDR, IN-ADDR.ARPA
   was also constrained such that delegations were only permitted along
   legacy, class A/B/C network number boundaries.  This created a
   difficult situation for more flexible, CIDR prefixes.  Consider a
   hypothetical large network provider named "BigNet" which has been
   allocated the block 10.4.0.0 through 10.7.255.0 (the CIDR prefix
   10.4.0.0/14).  Under the old delegation policies, the top-level IN-
   ADDR.ARPA domain servers would need to have 1024 entries of the form:

       0.4.10.IN-ADDR.ARPA.   IN      NS      NS1.BIG.NET.

       1.4.10.IN-ADDR.ARPA.   IN      NS      NS1.BIG.NET.

               ....

       255.7.10.IN-ADDR.ARPA. IN      NS      NS1.BIG.NET.

   By revising the policy as described above, this was reduced to four
   delegation records:




Fuller & Li             Expires October 10, 2005               [Page 17]

Internet-Draft            CIDR Address Strategy               April 2005


       4.10.IN-ADDR.ARPA.     IN      NS      NS1.BIG.NET.

       5.10.IN-ADDR.ARPA.     IN      NS      NS1.BIG.NET.

       6.10.IN-ADDR.ARPA.     IN      NS      NS1.BIG.NET.

       7.10.IN-ADDR.ARPA.     IN      NS      NS1.BIG.NET.

   The provider then maintains further delegations of naming authority
   for each individual /24 which it assigns, rather than having each
   registered separately.  Note that due to the way the DNS is designed,
   it is still possible for the top-level IN-ADDR.ARPA name servers to
   maintain the delegation information for individual networks for which
   the provider is unwilling or unable to do so.  The example above
   illustrates only the records for a single name server.  In the normal
   case, there are usually several name servers for each domain, thus
   the size of the examples will double or triple in the common cases.

   For BIG.NET to assign a blocks smaller than /24 to its customers, it
   can similarly delegate DNS authority for those addresses.  For
   example, if it were to assign 10.4.99.64/26 to its customer
   CUSTONE.COM and 10.4.99.128/27 to its customer CUSTTWO.COM, it could
   add the following records to delegate DNS for the addresses to those
   customers:

       64.99.4.10.IN-ADDR.ARPA.    IN    NS    NS1.CUSTONE.COM.

       65.99.4.10.IN-ADDR.ARPA.    IN    NS    NS1.CUSTONE.COM.

              ....

       127.99.4.10.IN-ADDR.ARPA.   IN    NS    NS1.CUSTONE.COM

       128.99.4.10.IN-ADDR.ARPA.   IN    NS    NS1.CUSTTWO.COM

       129.99.4.10.IN-ADDR.ARPA.   IN    NS    NS1.CUSTTWO.COM

              ....

       159.99.4.10.IN-ADDR.ARPA.   IN    NS    NS1.CUSTTWO.COM

   And if BIG.NET also assigned 10.4.99.160/30 to CUSTTHREE.COM but this
   customer did not want to run its own DNS, BIG.NET could provide that
   service for the customer by installing the appropriate PTR records:







Fuller & Li             Expires October 10, 2005               [Page 18]

Internet-Draft            CIDR Address Strategy               April 2005


       160.99.4.10.IN-ADDR.ARPA.   IN    PTR   NET.CUSTTHREE.COM.

       161.99.4.10.IN-ADDR.ARPA.   IN    PTR   HOST1.CUSTTHREE.COM.

       162.99.4.10.IN-ADDR.ARPA.   IN    PTR   HOST2.CUSTTHREE.COM.

       163.99.4.10.IN-ADDR.ARPA.   IN    PTR   BCAST.CUSTTHREE.COM.

   See [RFC2317] for a much more detailed discussion of DNS delegation
   with classless addressing.

7.  Transition to a long term solution

   CIDR was designed to be a short-term solution to the problems of
   routing state and address depletion on the IPv4 Internet.  It does
   not change the fundamental Internet routing or addressing
   architectures.  It is not expected to affect any plans for transition
   to a more long-term solution except, perhaps, by delaying the urgency
   of developing such a solution.

8.  Analysis of CIDR's effect on global routing state

   When CIDR was first proposed in the early 1990s, the original authors
   made some observations about the growth rate of global routing state
   and offered projections on how CIDR deployment would, hopefully,
   reduce what appeared to be exponential growth to a more sustainable
   rate.  Since that deployment, an ongoing effort, called "The CIDR
   Report" [CRPT] has attempted to quantify and track that growth rate.
   What follows is a brief summary of the CIDR report as of March, 2005,
   with an attempt to explain the various patterns of and change in
   growth rate that have occurred since measurements of the size of
   global routing state began in 1988.

   Examining the graph of "Active BGP Table Entries" [CBGP] there appear
   to be several different growth trends with distinct inflection points
   reflecting changes in policy and practice.  The trends and events
   which are believed to have caused them were:

   1.  Exponential growth at the far left of the graph.  This represents
       the period of early expansion and commercialization of the former
       research network, from the late 1980s through approximately 1994.
       The major driver for this growth was a lack of aggregation
       capability for transit providers, and the widespread use of
       legacy Class C allocations for end sites.  Each time a new site
       was connected to the global Internet, one or more new routing
       entries were generated.





Fuller & Li             Expires October 10, 2005               [Page 19]

Internet-Draft            CIDR Address Strategy               April 2005


   2.  Acceleration of the exponential trend in late 1993 and early 1994
       as CIDR supernet" blocks were first assigned by the NIC and
       routed as separate legacy class-C networks by service provider.

   3.  A sharp drop in 1994 as BGP4 deployment by providers allowed
       aggregation of the "supernet" blocks.  Note that the periods of
       largest declines in the number of routing table entries typically
       correspond to the weeks following each meeting of the IETF CIDR
       Deployment Working Group.

   4.  Roughly linear growth from mid-1994 to early 1999 as CIDR-based
       address assignments were made and aggregated routes added
       throughout the network.

   5.  A new period of exponential growth again from early 1999 until
       2001 as the "high-tech bubble" fueled both rapid expansion of
       Internet as well as a large increase in more-specific route
       advertisements for multi-homing and traffic engineering.

   6.  Flattening of growth through 2001 caused by a combination of the
       "dot-com bust", which caused many organizations to cease
       operations, and the "CIDR police" [CPOL] work aimed at improving
       aggregation efficiency.

   7.  Roughly linear growth through 2002 and 2003.  This most likely
       represents a resumption of the "normal" growth rate observed
       before the "bubble" as well as an end to the "CIDR Police"
       effort.

   8.  A more recent trend of exponential growth beginning in 2004.  The
       best explanation would seem to be an improvement of the global
       economy driving increased expansion of the Internet and the
       continued absence of the "CIDR Police" effort, which previously
       served as an educational tool for new providers to improve
       aggregation efficiency.  There have also been some cases where
       service providers have deliberately de-aggregated prefixes in an
       attempt to mitigate security problems caused by conflicting route
       advertisements (see Section 10).  While this behavior may solve
       the short-term problems seen by such providers, it is
       fundamentally non-scalable and quite detrimental to the community
       as a whole.  In addition, there appear to be many providers
       advertising both their allocated prefixes and all of the /24
       components of them, probably due to a lack of consistent current
       information about recommended routing configuration.







Fuller & Li             Expires October 10, 2005               [Page 20]

Internet-Draft            CIDR Address Strategy               April 2005


9.  Conclusions and Recommendations

   In 1992, when CIDR was first developed, there were serious problems
   facing the continued growth of the Internet.  Growth in routing state
   complexity, and the rapid increase in consumption of address space
   made it appear that one or both problems would preclude continued
   growth of the Internet within a few short years.

   Deployment of CIDR, in combination with BGP4's support for carrying
   classless prefix routes, alleviated the short-term crisis.  It was
   only through a concerted effort by both the equipment manufacturers
   and the provider community that this was achieved.  The threat (and,
   perhaps in some cases, actual implementation of) charging networks
   for advertising prefixes may have offered an additional incentive to
   share the address space, and hence the associated costs of
   advertising routes to service providers.

   The IPv4 routing system architecture carries topology information
   based on aggregate address advertisements and a collection of more-
   specific advertisements that are associated with traffic engineering,
   multi-homing and local configuration.  As of March, 2005, the base
   aggregate address load in the routing system has some 75,000 entries.
   Approximately 85,000 additional entries are more specific entries of
   this base "root" collection.  There is reason to believe that many of
   these additional entries are exist to solve problems of regional or
   even local scope and should not need to be globally propagated.

   An obvious question to ask is whether CIDR can continue to be a
   viable approach to keeping global routing state growth and address
   space depletion at sustainable rates.  Recent measurements indicate
   that exponential growth has resumed but further analysis suggests
   that this trend can be mitigated by a more active effort to educate
   service providers on efficient aggregation strategies and proper
   equipment configuration.  Looking farther forward, there is a clear
   need for better multi-homing technology that does not require global
   routing state for each site and for methods of performing traffic
   load balancing that do not require adding even more state.  Without
   such developments and in the absence of major architectural change,
   aggregation is the only tool available for making routing scale in
   the global Internet.

10.  Security Considerations

   The introduction of routing protocols which support classless
   prefixes and a move to a forwarding model that mandates that more-
   specific (longest-match) routes be preferred when they overlap with
   routes to less-specific prefixes introduces at least two security
   concerns:



Fuller & Li             Expires October 10, 2005               [Page 21]

Internet-Draft            CIDR Address Strategy               April 2005


      Traffic can be hijacked by advertising a prefix for a given
      destination that is more specific than the aggregate that is
      normally advertised for that destination.  For example, assume a
      popular end system with address 192.168.17.100 that is connected
      to a service provider that advertises 192.168.16.0/20.  A
      malicious network operator interested in intercepting traffic for
      this site might advertise, or at least attempt to advertise,
      192.168.17.0/24 into the global routing system.  Because this
      prefix is more-specific than the "normal" prefix, traffic will be
      diverted away from the legitimate end system and to the network
      owned by the malicious operator.  Prior to the advent of CIDR, it
      was possible to induce traffic from some parts of the network to
      follow a false advertisement that exactly matched a particular
      network number; CIDR makes this problem somewhat worse, since
      longest-match routing generally causes all traffic to prefer more-
      specific routes over less-specific routes.  The remedy for the
      CIDR-based attack, though, is the same as for a pre-CIDR-based
      attack: establishment of trust relationships between providers,
      coupled with and strong route policy filters at provider borders.
      Unfortunately, the implementation of such filters is difficult in
      the highly de-centralized Internet.  As a workaround, many
      providers do implement generic filters that set upper bounds,
      derived from RIR guidelines for the sizes of blocks that they
      allocate, on the lengths of prefixes that are accepted from other
      providers.  It is worth noting that "spammers" have been observed
      using this sort of attack to temporarily hijack address space in
      order to hide the origin of the traffic ("spam" email messages)
      that they generate.

      Denial-of-service attacks can be launched against many parts of
      the Internet infrastructure by advertising a large number of
      routes into the system.  Such an attack is intended to cause
      router failures by overflowing routing and forwarding tables.  A
      good example of a non-malicious incident which caused this sort of
      failure was the infamous "AS 7007" event [7007] where a router
      mis-configuration by an operator caused a huge number of invalid
      routes to be propagated through the global routing system.  Again,
      this sort of attack is not really new with CIDR; using legacy
      class A/B/C routes, it was possible to advertise a maximum of
      16843008 unique network numbers into the global routing system, a
      number which is sufficient to cause problems for even the most
      modern routing equipment made in 2005.  What is different is that
      the moderate complexity of correctly configuring routers in the
      presence of CIDR does tend to make accidental "attacks" of this
      sort more likely.  Measures to prevent this sort of attack are
      much the same as those described above for the hijacking, with the
      addition that best common practice is to also configure a
      reasonable maximum number of prefixes that a border router will



Fuller & Li             Expires October 10, 2005               [Page 22]

Internet-Draft            CIDR Address Strategy               April 2005


      accept from its neighbors.

      Note that this is not intended to be an exhaustive analysis of the
      sorts of attacks that CIDR makes easier; a more comprehensive
      analysis of security vulnerabilities in the global routing system
      is beyond the scope of this document.


11.  Acknowledgments

   The authors wish to express appreciation to the other original
   authors of RFC1519 (Kannan Varadhan, Jessica Yu), to the ROAD group
   with whom many of the ideas behind CIDR were inspired and developed,
   and to the early reviewers of this re-spun version of the document
   (Barry Greene, Geoff Huston, Danny McPherson, Dave Meyer, Eliot Lear,
   Bill Norton, Ted Seely, Philip Smith) whose comments, corrections,
   and suggestions were invaluable.

12.  References

12.1  Normative References

   [RFC791]  Postel, J., "Internet Protocol", RFC 791, September 1981.

12.2  Informative References

   [RFC1338]  Fuller, V., Li, T., Varadhan, K., and J. Yu,
              "Supernetting: an Address Assignment and Aggregation
              Strategy", RFC 1338, June 1992.

   [RFC1519]  Fuller, V., Li, T., Varadhan, K., and J. Yu, "Classless
              Inter-Domain Routing: an Address Assignment and
              Aggregation Strategy", RFC 1519, September 1993.

   [IANA]     "Internet Assigned Numbers Authority",
              <http://www.iana.org>.

   [NRO]      "Number Resource Organization", <http://www.nro.net>.

   [RFC1380]  Gross, P. and P. Almquist, "IESG Deliberations on Routing
              and Addressing", RFC 1380, November 1992.

   [LWRD]     "The Long and Winding Road",
              <http://rms46.vlsm.org/1/42.html>.

   [RFC2178]  Moy, J., "The OSPF Specification Version 2", RFC 2178,
              July 1997.




Fuller & Li             Expires October 10, 2005               [Page 23]

Internet-Draft            CIDR Address Strategy               April 2005


   [RFC1195]  Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
              dual environments", RFC 1195, December 1990.

   [RFC2453]  Malkin, G., "RIP Version 2", RFC 2453, November 1998.

   [RFC1771]  Rekhter, Y. and T. Li, "A Border Gateway Protocol 4
              (BGP-4)", RFC 1771, March 1995.

   [RFC1058]  Hedrick, C., "Routing Information Protocol", RFC 1058,
              June 1988.

   [RFC904]   Mills, D., "Exterior Gateway Protocol formal
              specification", RFC 904, April 1984.

   [RFC3021]  Retana, A., White, R., Fuller, V., and D. McPherson,
              "Using 31-Bit Prefixes on IPv4 Point-to-Point Links",
              RFC 3021, December 2000.

   [RFC2131]  Droms, R., "Dynamic Host Configuration Protocol",
              RFC 2131, March 1997.

   [RIPE]     "RIPE Network Coordination Centre", <http://www.ripe.net>.

   [RFC1518]  Rekhter, Y. and T. Li, "An Architecture for IP Address
              Allocation with CIDR", RFC 1518, September 1993.

   [RFC2317]  Eidnes, H., de Groot, G., and P. Vixie, "Classless IN-
              ADDR.ARPA delegation", RFC 2317, March 1998.

   [CRPT]     "The CIDR Report", <http://www.cidr-report.org/>.

   [CBGP]     "Graph: Active BGP Table Entries, 1988 to Present",
              <http://bgp.potaroo.net/as4637/>.

   [CPOL]     "CIDR Police - Please Pull Over and Show Us Your BGP",
              <http://www.nanog.org/mtg-0302/cidr.html>.

   [7007]     "NANOG mailing list discussion of the "AS 7007" incident",
              <http://www.merit.edu/mail.archives/nanog/1997-04/
              msg00340.html>.











Fuller & Li             Expires October 10, 2005               [Page 24]

Internet-Draft            CIDR Address Strategy               April 2005


Authors' Addresses

   Vince Fuller
   170 W. Tasman Drive
   San Jose, CA  95134
   USA

   Email: vaf@cisco.com


   Tony Li
   170 W. Tasman Drive
   San Jose, CA  95134
   USA

   Email: tli@cisco.com



































Fuller & Li             Expires October 10, 2005               [Page 25]

Internet-Draft            CIDR Address Strategy               April 2005


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2005).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Fuller & Li             Expires October 10, 2005               [Page 26]
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr 12 03:14:29 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02367
	for <grow-archive@lists.ietf.org>; Tue, 12 Apr 2005 03:14:28 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3C7CZ9e013484;
	Tue, 12 Apr 2005 00:12:35 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3C7CZiM013483;
	Tue, 12 Apr 2005 00:12:35 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3C7CXFa013448
	for <grow@lists.uoregon.edu>; Tue, 12 Apr 2005 00:12:34 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j3C7CNE03954;
	Tue, 12 Apr 2005 10:12:23 +0300
Date: Tue, 12 Apr 2005 10:12:22 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: David Meyer <dmm@1-4-5.net>
cc: grow@lists.uoregon.edu, gih@apnic.net, Timothy.Griffin@cl.cam.ac.uk
Subject: Re: grow: WGLC for BGP Wedgies (draft-ietf-grow-bgp-wedgies-01.txt)
In-Reply-To: <20050330194525.GA5730@1-4-5.net>
Message-ID: <Pine.LNX.4.61.0504121010180.3431@netcore.fi>
References: <20050330194525.GA5730@1-4-5.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

On Wed, 30 Mar 2005, David Meyer wrote:
> 	This note starts the WG Last Call for comments on
> 	draft-ietf-grow-bgp-wedgies-01.txt, "BGP Wedgies".
> 	It can be found on
>
> 	ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-bgp-wedgies-01.txt
>
> 	Please review the document carefully, and send your
> 	feedback to the list.  Please also indicate whether or
> 	not you believe that this document is ready to go to the
> 	IESG. Note that this is a somewhat unusal case as the
> 	IESG requested this document.

Looks good.

I noticed two things which can be fixed when the document is respun:

  - s/suppoprt/support/
  - add a dummy IANA Considerations section saying that there are no 
IANA considerations and that the section can be removed by the 
rfc-editor prior to publication.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr 12 03:34:19 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA03406
	for <grow-archive@lists.ietf.org>; Tue, 12 Apr 2005 03:34:19 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3C7XDZD024440;
	Tue, 12 Apr 2005 00:33:13 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3C7XDUC024439;
	Tue, 12 Apr 2005 00:33:13 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3C7XBhN024393
	for <grow@lists.uoregon.edu>; Tue, 12 Apr 2005 00:33:12 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j3C7WxS04416;
	Tue, 12 Apr 2005 10:32:59 +0300
Date: Tue, 12 Apr 2005 10:32:59 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: David Meyer <dmm@1-4-5.net>
cc: grow@lists.uoregon.edu, VijayGill9@aol.com, danny@arbor.net
Subject: Re: grow: WGLC for BGP MED Considerations (draft-ietf-grow-bgp-med-considerations-03.txt)
In-Reply-To: <20050330194917.GA5814@1-4-5.net>
Message-ID: <Pine.LNX.4.61.0504121024390.3431@netcore.fi>
References: <20050330194917.GA5814@1-4-5.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

On Wed, 30 Mar 2005, David Meyer wrote:
> 	Please review the document carefully, and send your
> 	feedback to the list.  Please also indicate whether or
> 	not you believe that this document is ready to go to the
> 	IESG. Note that this is a somewhat unusal case as the
> 	IESG requested this document.
>
> 	This Last Call will end on 13 Apr 2004 at 1400 PST
> 	(UTC/GMT-8).

I think it's getting better.  However, I didn't -- at least right out 
-- see a resolution to a couple of more significant issues raised 
about -02.  Copied below..

Two new editorial issues spotted:
- add a dummy IANA considerations section
- there are a couple of lines (in the boilerplate) that go beyond the 
limit of 72 chars/line

=== (from Danny's message on the list on September 2004) ====
> substantial
> -----------
>
>    If one transit provider uses hot potato routing and another uses cold
>    potato, traffic between the two tends to be more symmetric.
>    Depending on the business relationships, if one provider has more
>    capacity or a significantly less congested backbone network, then
>    that provider may use cold potato routing.  An example of widespread
>    use of cold potato routing was the NSF funded NSFNET backbone and NSF
>    funded regional networks in the mid 1990s.
>
> ==> this begs the question of "what about hot-potato - hot-potato or
> cold-potato -cold-potato".  It seems to be implicit that these are
> likely asymmetric, but that may not need to be the case, especially
> with the latter.  This should probably be spelled out.

I'll clean up the wording..

>    As a result of implementation inconsistencies and protocol revision
>    variances, many network operators today explicitly reset all MED
>    values on ingress to conform to their internal routing policies
>    (i.e., to include policy that requires that MED values of 0 and
>    2^32-1 NOT be used in configurations, whether the MEDs are directly
>    computed or configured), so as to not have to rely on all their
>    routers having the same missing-MED behavior.
>
> ==> I was slightly confused by this, esp. 'reset', and the text on MED
> values of 0 and 2^32-1.  The point just is that the network operators
> ensure to map a missing MED to MED=0 in ingress if they use MEDs at
> all (at least that's what we do -- I fail to see any reason to avoid
> MED=0, because it doesn't cause problems.  The missing MED does.).

And if they don't use MEDs, they does this implicitly by
setting all the MED values the same on ingress to the AS.
That was the point.  I'll look to clean it up.

[...]
> ==> Actually, I think you should re-read the doc with 'comparing MEDs
> and ASs' in mind.  It seems that in different sections
> (implementation/protocol vs deployment) there are different kinds of
> advice what seems to be the best thing to do.  These probably need a
> bit aligning or at least some applicability if the recommendations to
> different people are different.

The recommendations to different people aren't different, but I
do understand your point.  I'll see if there's any better way
to align.

[ editorials.. ]
>    Comparing MEDs between differing adjacent autonomous systems (which
>    will be discussed in later sections),
>
> ==> it was in the previous section..., and later in sect 3.1 ? --
> please put in a more explicit pointer.

I'll fix..
====================


-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr 12 06:11:35 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15078
	for <grow-archive@lists.ietf.org>; Tue, 12 Apr 2005 06:11:34 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CA9WNg008263;
	Tue, 12 Apr 2005 03:09:32 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3CA9WIE008262;
	Tue, 12 Apr 2005 03:09:32 -0700 (PDT)
Received: from kahuna.telstra.net (kahuna.telstra.net [203.50.0.6])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CA9UGs008221
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <grow@lists.uoregon.edu>; Tue, 12 Apr 2005 03:09:31 -0700 (PDT)
Received: from gihz1.apnic.net (dhcp12.potaroo.net [203.10.60.12])
	by kahuna.telstra.net (8.12.3/8.11.3) with ESMTP id j3CA8mXt054239;
	Tue, 12 Apr 2005 20:08:49 +1000 (EST)
	(envelope-from gih@apnic.net)
Message-Id: <6.0.1.1.2.20050412200825.02d86430@kahuna.telstra.net>
X-Sender: gih@kahuna.telstra.net
X-Mailer: QUALCOMM Windows Eudora Version 6.0.1.1
Date: Tue, 12 Apr 2005 20:08:50 +1000
To: Pekka Savola <pekkas@netcore.fi>, David Meyer <dmm@1-4-5.net>
From: Geoff Huston <gih@apnic.net>
Subject: Re: grow: WGLC for BGP Wedgies
  (draft-ietf-grow-bgp-wedgies-01.txt)
Cc: grow@lists.uoregon.edu, Timothy.Griffin@cl.cam.ac.uk
In-Reply-To: <Pine.LNX.4.61.0504121010180.3431@netcore.fi>
References: <20050330194525.GA5730@1-4-5.net>
 <Pine.LNX.4.61.0504121010180.3431@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

Thanks indeed for these comments Pekka.

regards,

    Geoff


At 05:12 PM 12/04/2005, Pekka Savola wrote:
>On Wed, 30 Mar 2005, David Meyer wrote:
>>         This note starts the WG Last Call for comments on
>>         draft-ietf-grow-bgp-wedgies-01.txt, "BGP Wedgies".
>>         It can be found on
>>
>> 
>>ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-bgp-wedgies-01.txt
>>
>>         Please review the document carefully, and send your
>>         feedback to the list.  Please also indicate whether or
>>         not you believe that this document is ready to go to the
>>         IESG. Note that this is a somewhat unusal case as the
>>         IESG requested this document.
>
>Looks good.
>
>I noticed two things which can be fixed when the document is respun:
>
>  - s/suppoprt/support/
>  - add a dummy IANA Considerations section saying that there are no IANA 
> considerations and that the section can be removed by the rfc-editor 
> prior to publication.
>
>--
>Pekka Savola                 "You each name yourselves king, yet the
>Netcore Oy                    kingdom bleeds."
>Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
>_________________________________________________________________
>web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
>web archive:        http://darkwing.uoregon.edu/~llynch/grow/


_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From ayala@mailAccount.com  Tue Apr 12 07:08:36 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19405;
	Tue, 12 Apr 2005 07:08:36 -0400 (EDT)
Received: from [222.113.76.192] (helo=132.151.6.1)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1DLJPa-0005Cy-TK; Tue, 12 Apr 2005 07:18:33 -0400
X-Apparently-To: gcunning@ietf.org
X-Sieve: CMU Sieve 2.2
Received: from metallurgic.colossus.pochta.ru ([unix socket])
         by butyric.adam.pochta.ru (Cyrus v2.2.9) with LMTPA;
         Tue, 12 Apr 2005 15:04:35 +0300
Date: Tue, 12 Apr 2005 07:09:35 -0500
From: "Antwan Bernal" <ayala@mailAccount.com>
Message-Id: <CFE1.AA79.9A31-003068198B8C@mac.com>
X-Accept-Language: en,zh-TW,zh-CN,zh,ja,ko,tr,ru
To: gcunning@ietf.org
Cc: gency@ietf.org, geopriv@ietf.org, geopriv-admin@ietf.org,
        geopriv-web-archive@ietf.org, gga8k2ijd9ai7232@ietf.org,
        ghostsender-a.3feet.com@ietf.org, grow-archive@ietf.org
Subject: Save hundreds every month on low rates
X-Mailer: Forte Agent 1.91/32.564
X-Spam-Score: 19.6 (+++++++++++++++++++)
X-Spam-Flag: YES
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a


Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.mrg-now-yes.com/sign.asp



 Best Regards,

 Rob Judd
 
 to be remov(ed:	http://www.mrg-now-yes.com/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From madkins@emailaccount.com  Tue Apr 12 07:11:07 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19551;
	Tue, 12 Apr 2005 07:11:07 -0400 (EDT)
Received: from [222.111.73.108] (helo=132.151.6.1)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1DLJS2-0005G4-7D; Tue, 12 Apr 2005 07:21:04 -0400
X-Apparently-To: gcunning@ietf.org
X-Sieve: CMU Sieve 2.2
Received: from from.message.pochta.ru ([unix socket])
         by balustrade.prophylactic.pochta.ru (Cyrus v2.2.7) with LMTPA;
         Tue, 12 Apr 2005 13:02:12 +0100
Date: Tue, 12 Apr 2005 07:02:12 -0500
From: "Greta Sneed" <madkins@emailaccount.com>
Message-Id: <CFE9.AA79.9A31-003046698B8C@mac.com>
X-Accept-Language: en,zh-TW,zh-CN,zh,ja,ko,tr,ru
To: gcunning@ietf.org
Cc: gency@ietf.org, geopriv@ietf.org, geopriv-admin@ietf.org,
        geopriv-web-archive@ietf.org, gga8k2ijd9ai7232@ietf.org,
        ghostsender-a.3feet.com@ietf.org, grow-archive@ietf.org, gsmp@ietf.org,
        gsmp-admin@ietf.org, gsmp-archive@ietf.org, gsmp-web-archive@ietf.org
Subject: Save hundreds every month on low rates
X-Mailer: Forte Agent 1.91/32.564
X-Spam-Score: 10.2 (++++++++++)
X-Spam-Flag: YES
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a


Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.mrg-now-yes.com/sign.asp



 Best Regards,

 Keith Manley
 
 to be remov(ed:	http://www.mrg-now-yes.com/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From owner-grow@lists.uoregon.edu  Tue Apr 12 11:23:55 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07867
	for <grow-archive@lists.ietf.org>; Tue, 12 Apr 2005 11:23:50 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CFKsvt004147;
	Tue, 12 Apr 2005 08:20:54 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3CFKsge004142;
	Tue, 12 Apr 2005 08:20:54 -0700 (PDT)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CFKrxC004124
	for <grow@lists.uoregon.edu>; Tue, 12 Apr 2005 08:20:53 -0700 (PDT)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.2/8.13.2) with ESMTP id j3CFKdtD010968;
	Tue, 12 Apr 2005 08:20:39 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.2/8.12.11/Submit) id j3CFKU3E010967;
	Tue, 12 Apr 2005 08:20:30 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Tue, 12 Apr 2005 08:20:30 -0700
From: David Meyer <dmm@1-4-5.net>
To: Pekka Savola <pekkas@netcore.fi>
Cc: grow@lists.uoregon.edu, VijayGill9@aol.com, danny@arbor.net
Subject: Re: grow: WGLC for BGP MED Considerations (draft-ietf-grow-bgp-med-considerations-03.txt)
Message-ID: <20050412152030.GA10958@1-4-5.net>
References: <20050330194917.GA5814@1-4-5.net> <Pine.LNX.4.61.0504121024390.3431@netcore.fi>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn"
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.61.0504121024390.3431@netcore.fi>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader, Star Wars Episode IV.
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk


--bp/iNruPH9dso1Pn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

	Pekka,

	Thanks for the close reading.

	Dave

On Tue, Apr 12, 2005 at 10:32:59AM +0300, Pekka Savola wrote:
> On Wed, 30 Mar 2005, David Meyer wrote:
> >	Please review the document carefully, and send your
> >	feedback to the list.  Please also indicate whether or
> >	not you believe that this document is ready to go to the
> >	IESG. Note that this is a somewhat unusal case as the
> >	IESG requested this document.
> >
> >	This Last Call will end on 13 Apr 2004 at 1400 PST
> >	(UTC/GMT-8).
>=20
> I think it's getting better.  However, I didn't -- at least right out=20
> -- see a resolution to a couple of more significant issues raised=20
> about -02.  Copied below..
>=20
> Two new editorial issues spotted:
> - add a dummy IANA considerations section
> - there are a couple of lines (in the boilerplate) that go beyond the=20
> limit of 72 chars/line
>=20
> =3D=3D=3D (from Danny's message on the list on September 2004) =3D=3D=3D=
=3D
> >substantial
> >-----------
> >
> >   If one transit provider uses hot potato routing and another uses cold
> >   potato, traffic between the two tends to be more symmetric.
> >   Depending on the business relationships, if one provider has more
> >   capacity or a significantly less congested backbone network, then
> >   that provider may use cold potato routing.  An example of widespread
> >   use of cold potato routing was the NSF funded NSFNET backbone and NSF
> >   funded regional networks in the mid 1990s.
> >
> >=3D=3D> this begs the question of "what about hot-potato - hot-potato or
> >cold-potato -cold-potato".  It seems to be implicit that these are
> >likely asymmetric, but that may not need to be the case, especially
> >with the latter.  This should probably be spelled out.
>=20
> I'll clean up the wording..
>=20
> >   As a result of implementation inconsistencies and protocol revision
> >   variances, many network operators today explicitly reset all MED
> >   values on ingress to conform to their internal routing policies
> >   (i.e., to include policy that requires that MED values of 0 and
> >   2^32-1 NOT be used in configurations, whether the MEDs are directly
> >   computed or configured), so as to not have to rely on all their
> >   routers having the same missing-MED behavior.
> >
> >=3D=3D> I was slightly confused by this, esp. 'reset', and the text on M=
ED
> >values of 0 and 2^32-1.  The point just is that the network operators
> >ensure to map a missing MED to MED=3D0 in ingress if they use MEDs at
> >all (at least that's what we do -- I fail to see any reason to avoid
> >MED=3D0, because it doesn't cause problems.  The missing MED does.).
>=20
> And if they don't use MEDs, they does this implicitly by
> setting all the MED values the same on ingress to the AS.
> That was the point.  I'll look to clean it up.
>=20
> [...]
> >=3D=3D> Actually, I think you should re-read the doc with 'comparing MEDs
> >and ASs' in mind.  It seems that in different sections
> >(implementation/protocol vs deployment) there are different kinds of
> >advice what seems to be the best thing to do.  These probably need a
> >bit aligning or at least some applicability if the recommendations to
> >different people are different.
>=20
> The recommendations to different people aren't different, but I
> do understand your point.  I'll see if there's any better way
> to align.
>=20
> [ editorials.. ]
> >   Comparing MEDs between differing adjacent autonomous systems (which
> >   will be discussed in later sections),
> >
> >=3D=3D> it was in the previous section..., and later in sect 3.1 ? --
> >please put in a more explicit pointer.
>=20
> I'll fix..
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20
> --=20
> Pekka Savola                 "You each name yourselves king, yet the
> Netcore Oy                    kingdom bleeds."
> Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--bp/iNruPH9dso1Pn
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCW+c+ORgD1qCZ2KcRAoUwAJ9nrmQEsywickp821VTxekJ3I93/QCdEEMp
PATTmLCRfNnTqr7dKoMASvQ=
=qoIq
-----END PGP SIGNATURE-----

--bp/iNruPH9dso1Pn--
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr 12 12:15:47 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11417
	for <grow-archive@lists.ietf.org>; Tue, 12 Apr 2005 12:15:45 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CGDo1n026515;
	Tue, 12 Apr 2005 09:13:50 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3CGDool026509;
	Tue, 12 Apr 2005 09:13:50 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3C72TbI007271
	for <grow@lists.uoregon.edu>; Tue, 12 Apr 2005 00:02:30 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j3C72Ie03757;
	Tue, 12 Apr 2005 10:02:18 +0300
Date: Tue, 12 Apr 2005 10:02:18 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Vince Fuller <vaf@cisco.com>
cc: grow@lists.uoregon.edu
Subject: Re: grow: draft of new RFC1519 replacement
In-Reply-To: <20050411170200.GA11870@vaf-lnx1.cisco.com>
Message-ID: <Pine.LNX.4.61.0504120957010.3431@netcore.fi>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

On Mon, 11 Apr 2005, Vince Fuller wrote:
> As part of the NEWTRK effort, the CIDR document (RFC1519) is being updated.
>
> What follows is a current draft of the new document. At this point, it is
> not clear whether this will become a GROW WG draft but the authors would
> appreciate review and comments from the members of this list.

A couple of high-level bits,

RFC-editor's search finds 8 current documents which have "CIDR" in
their title.

Which ones does this obsolete?  (I'd hope as many as
possible.)

Which documents (apart fromt he CIDR ones) does this Update (if any)?



> Classless Inter-Domain Routing (CIDR): The Internet Address Assignment
>                          and Aggregation Plan
>                        draft-vaf-cidrupdate-00
>
> Status of this Memo
>
>   This document is an Internet-Draft and is subject to all provisions
>   of Section 3 of RFC 3667.  By submitting this Internet-Draft, each
>   author represents that any applicable patent or other IPR claims of
>   which he or she is aware have been or will be disclosed, and any of
>   which he or she become aware will be disclosed, in accordance with
>   RFC 3668.
>
>   Internet-Drafts are working documents of the Internet Engineering
>   Task Force (IETF), its areas, and its working groups.  Note that
>   other groups may also distribute working documents as Internet-
>   Drafts.
>
>   Internet-Drafts are draft documents valid for a maximum of six months
>   and may be updated, replaced, or obsoleted by other documents at any
>   time.  It is inappropriate to use Internet-Drafts as reference
>   material or to cite them other than as "work in progress."
>
>   The list of current Internet-Drafts can be accessed at
>   http://www.ietf.org/ietf/1id-abstracts.txt.
>
>   The list of Internet-Draft Shadow Directories can be accessed at
>   http://www.ietf.org/shadow.html.
>
>   This Internet-Draft will expire on October 10, 2005.
>
> Copyright Notice
>
>   Copyright (C) The Internet Society (2005).
>
> Abstract
>
>   This memo discusses the strategy for address assignment of the
>   existing 32-bit IPv4 address space with a view toward conserving the
>   address space and limiting the growth rate of global routing state.
>   This document is intended as a replacement to the original CIDR spec
>   [RFC1519] with changes made both to clarify the concepts it
>
>
>
> Fuller & Li             Expires October 10, 2005                [Page 1]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   introduced and, after more than twelve years, to update the Internet
>   community on the results of deploying the technology it described.
>
> Table of Contents
>
>   1.   History and Problem Description  . . . . . . . . . . . . . .   3
>   2.   Classless addressing as a solution . . . . . . . . . . . . .   4
>     2.1  Basic concept and prefix notation  . . . . . . . . . . . .   5
>   3.   Address assignment and routing aggregation . . . . . . . . .   7
>     3.1  Aggregation efficiency and limitations . . . . . . . . . .   7
>     3.2  Distributed assignment of address space  . . . . . . . . .   9
>   4.   Routing implementation considerations  . . . . . . . . . . .  10
>     4.1  Rules for route advertisement  . . . . . . . . . . . . . .  10
>     4.2  How the rules work . . . . . . . . . . . . . . . . . . . .  11
>     4.3  A note on prefix filter formats  . . . . . . . . . . . . .  12
>     4.4  Responsibility for and configuration of aggregation  . . .  12
>     4.5  Route propagation and routing protocol considerations  . .  14
>   5.   Example of new address assignments and routing . . . . . . .  14
>     5.1  Address delegation . . . . . . . . . . . . . . . . . . . .  14
>     5.2  Routing advertisements . . . . . . . . . . . . . . . . . .  16
>   6.   Domain Name Service considerations . . . . . . . . . . . . .  17
>   7.   Transition to a long term solution . . . . . . . . . . . . .  19
>   8.   Analysis of CIDR's effect on global routing state  . . . . .  19
>   9.   Conclusions and Recommendations  . . . . . . . . . . . . . .  21
>   10.  Security Considerations  . . . . . . . . . . . . . . . . . .  21
>   11.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . .  23
>   12.  References . . . . . . . . . . . . . . . . . . . . . . . . .  23
>     12.1   Normative References . . . . . . . . . . . . . . . . . .  23
>     12.2   Informative References . . . . . . . . . . . . . . . . .  23
>        Authors' Addresses . . . . . . . . . . . . . . . . . . . . .  25
>        Intellectual Property and Copyright Statements . . . . . . .  26
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Fuller & Li             Expires October 10, 2005                [Page 2]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
> 1.  History and Problem Description
>
>   What is now known as the Internet started as a research project in
>   the 1970s to design and develop a set of protocols that could be used
>   with many different network technologies to provide a seamless, end-
>   to-end facility for interconnecting a diverse set of end systems.
>   When determining how the 32-bit address space would be used, certain
>   assumptions were made about the number of organizations to be
>   connected, the number of end systems per organization, and total
>   number of end systems on the network.  The end result was the
>   establishment (see [RFC791]) of three classes  of networks: class A
>   (most significant address bits '00'), with 128 possible networks each
>   with 16777216 end systems (minus special bit values reserved for
>   network/broadcast addresses); class B (MSB '10'), with 16384 possible
>   networks each with 65536 end systems (less reserved values); and
>   class C (MSB '110'), with 2097152 possible networks each with 254 end
>   systems (256 bit combinations minus the reserved all-zeros and all-
>   ones patterns).  The set of addresses with MSB '111' was reserved for
>   future use; parts of this were eventually defined (MSB '1110') for
>   use with IPv4 multicast and parts are still reserved as of the
>   writing of this document.
>
>   In the late 1980s, the expansion and commercialization of the former
>   research network resulted in the connection of many new organizations
>   to the rapidly-growing Internet and each new organization required an
>   address assignment according to the class A/B/C addressing plan.  As
>   demand for new network numbers, particularly in the class B space
>   started to take on what appeared to be an exponential growth rate,
>   some members of the operations and engineering community started to
>   have concerns over the long-term scaling properties of the class
>   A/B/C system and began thinking about how to modify network number
>   assignment policy and routing protocols to better accommodate the
>   growth.  In November, 1991, the IETF created the ROAD (Routing and
>   Addressing) group to examine the situation.  This group met in
>   January, 1992 and identified three major problems:
>
>   1.  Exhaustion of the class B network address space.  One fundamental
>       cause of this problem is the lack of a network class of a size
>       which is appropriate for mid-sized organization; class C, with a
>       maximum of 254 host addresses, is too small, while class B, which
>       allows up to 65534 host addresses, is too large for most
>       organizations but was the best fit available for use with
>       subnetting.
>
>   2.  Growth of routing tables in Internet routers beyond the ability
>       of current software, hardware, and people to effectively manage.
>
>
>
>
>
> Fuller & Li             Expires October 10, 2005                [Page 3]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   3.  Eventual exhaustion of the 32-bit IPv4 address space.
>
>   It was clear that then-current rates of Internet growth would cause
>   the first two problems to become critical some time between 1993 and
>   1995.  Work already in progress on topological assignment of
>   addressing for CLNS, which was presented to the community at the
>   Boulder IETF in December of 1990, led to thoughts on how to re-
>   structure the 32-bit IPv4 address space to increase its lifespan.
>   Work in the ROAD group followed and eventually resulted in the
>   publication of [RFC1338] and later [RFC1519].
>
>   The design and deployment of CIDR was intended to solve these
>   problems by providing a mechanism to slow the growth of global
>   routing tables and to reduce the rate of consumption of IPv4 address
>   space.  It did not and does not attempt to solve the third problem,
>   which is of a more long-term nature, but instead endeavors to ease
>   enough of the short to mid-term difficulties to allow the Internet to
>   continue to function efficiently while progress is made on a longer-
>   term solution.
>
>   More historical background on this effort and on the ROAD group may
>   be found in [RFC1380] and at [LWRD].
>
> 2.  Classless addressing as a solution
>
>   The solution that the community created was to deprecate the Class
>   A/B/C network address assignment system in favor of using
>   "classless", hierarchical blocks of IP addresses (referred to as
>   prefixes).  The assignment of prefixes is intended to roughly follow
>   the underlying Internet topology so that aggregation can be used to
>   facilitate scaling of the global routing system.  One implication of
>   this strategy is that prefix assignment and aggregation is generally
>   done according to provider-subscriber relationships, since that is
>   how the Internet topology is determined.
>
>   When originally proposed in [RFC1338] and [RFC1519], this addressing
>   plan was intended to be a relatively short-term response, lasting
>   approximately three to five years during which a more permanent
>   addressing and routing architecture would be designed and
>   implemented.  As can be inferred from the dates on the original
>   documents, CIDR has far outlasted its anticipated lifespan and has
>   become the mid-term solution to the problems described above.
>
>   Coupled with address management strategies implemented by the
>   Regional Internet Registries (see [NRO] for details), the deployment
>   of CIDR-style addressing has also reduced the rate at which IPv4
>   address space has been consumed, thus providing short-to-medium-term
>   relief to problem #3 described above.
>
>
>
> Fuller & Li             Expires October 10, 2005                [Page 4]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   Note that, as defined, this plan neither requires nor assumes the re-
>   assignment of those parts of the legacy "class C" space that are not
>   amenable to aggregation (sometimes called "the swamp").  Doing so
>   would somewhat reduce routing table sizes (current estimate is that
>   "the swamp" contains approximately 15,000 entries) though at a
>   significant renumbering cost.  Similarly, there is no hard
>   requirement that any end site renumber when changing transit service
>   provider but end sites are encouraged do so to eliminate the need for
>   explicit advertisement of their prefixes into the global routing
>   system.
>
> 2.1  Basic concept and prefix notation
>
>   In the simplest sense, the change from Class A/B/C network numbers to
>   classless prefixes is to make explicit which bits in a 32-bit IPv4
>   address are interpreted as the network number (or prefix) associated
>   with a site and which are the used to number individual end systems
>   within the site.  In CIDR notation, a prefix is shown as a 4-octet
>   quantity, just like a traditional IPv4 address or network number,
>   followed by the "/" (slash) character, followed by a decimal value
>   between 0 and 32 that describes the number of significant bits.
>
>   For example, the legacy "class B" network 172.16.0.0, with an implied
>   network mask of 255.255.0.0, is defined as the prefix 172.16.0.0/16,
>   the "/16" indicating that the mask to extract the network portion of
>   the prefix is a 32-bit value where the most significant 16 bits are
>   ones and the least significant 16 bits are zeros.  Similarly, the
>   legacy "class C" network number 192.168.99.0 is defined as the prefix
>   192.168.99.0/24 - the most significant 24 bits are ones and the least
>   significant 8 bits are zeros.
>
>   Using classless prefixes with explicit prefix lengths allows much
>   more flexible matching of address space blocks to actual need.  Where
>   formerly only three network sizes were available, prefixes may be
>   defined to describe any power-of-two-sized block of between one and
>   2^32 end system addresses.  In practice, the unallocated pool of
>   addresses is administered by the Internet Assigned Numbers Authority
>   ([IANA]).  The IANA makes allocations from this pool to Regional
>   Internet Registries, as required.  These allocations are made in
>   contiguous bit-aligned blocks of 2^24 addresses (a.k.a. /8 prefixes).
>   The RIRs, in turn, allocate or assign smaller address blocks to Local
>   Internet Registries (LIRs) or Internet Service Providers (ISPs).
>   These entities may make direct use of the assignment (as would
>   commonly be the case for an ISP) or may make further sub-allocations
>   of addresses to their customers.  These RIR address assignments vary
>   according to the needs of each ISP or LIR.  For example, a large ISP
>   might be allocated an address block of 2^17 addresses (a /15 prefix)
>   while a smaller ISP may be allocated an address block of 2^11
>
>
>
> Fuller & Li             Expires October 10, 2005                [Page 5]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   addresses (a /21 prefix).
>
>   Note that the terms "allocate" and "assign" have specific meaning in
>   the Internet address registry system; "allocate" refers to the
>   delegation of a block of address space to an organization which is
>   expected to perform further sub-delegations while "assign" is used
>   for sites that directly use (i.e. number individual hosts) the block
>   of addresses received.
>
>   The following table provides a convenient short-cut to all of the
>   CIDR prefix sizes, showing the number of addresses possible in each
>   prefix and the number of prefixes of that size that may be numbered
>   in the 32-bit IPv4 address space:
>
>
>       notation       addrs/block      # blocks
>       --------       -----------     ----------
>       n.n.n.n/32               1     4294967296    "host route"
>       n.n.n.x/31               2     2147483648    "[RFC3021] p2p link"
>       n.n.n.x/30               4     1073741824
>       n.n.n.x/29               8      536870912
>       n.n.n.x/28              16      268435456
>       n.n.n.x/27              32      134217728
>       n.n.n.x/26              64       67108864
>       n.n.n.x/25             128       33554432
>       n.n.n.0/24             256       16777216    legacy "class C"
>       n.n.x.0/23             512        8388608
>       n.n.x.0/22            1024        4194304
>       n.n.x.0/21            2048        2097152
>       n.n.x.0/20            4096        1048576
>       n.n.x.0/19            8192         524288
>       n.n.x.0/18           16384         262144
>       n.n.x.0/17           32768         131072
>       n.n.0.0/16           65536          65536    legacy "class B"
>       n.x.0.0/15          131072          32768
>       n.x.0.0/14          262144          16384
>       n.x.0.0/13          524288           8192
>       n.x.0.0/12         1048576           4096
>       n.x.0.0/11         2097152           2048
>       n.x.0.0/10         4194304           1024
>       n.x.0.0/9          8388608            512
>       n.0.0.0/8         16777216            256    legacy "class A"
>       x.0.0.0/7         33554432            128
>       x.0.0.0/6         67108864             64
>       x.0.0.0/5        134217728             32
>       x.0.0.0/4        268435456             16
>       x.0.0.0/3        536870912              8
>       x.0.0.0/2       1073741824              4
>
>
>
> Fuller & Li             Expires October 10, 2005                [Page 6]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>       x.0.0.0/1       2147483648              2
>       0.0.0.0/0       4294967296              1    "default route"
>
>   n is an 8-bit, decimal octet value.
>
>   x is a 1 to 7 bit value, base on the prefix length, shifted into the
>   most significant bits of the octet and converted into decimal form;
>   the least significant bits of the octet are zero.
>
>   In practice, prefixes of length shorter than 8 are not allocated or
>   assigned though routes to such short prefixes may exist in routing
>   tables if or when aggressive aggregation is performed.  As of the
>   writing of this document, no such routes are seen in the global
>   routing system but operator error and other events have caused some
>   of them (i.e. 128.0.0.0/1 and 192.0.0.0/2) to be observed in some
>   networks at some times in the past.
>
> 3.  Address assignment and routing aggregation
>
>   Classless addressing and routing was initially developed primarily to
>   improve the scaling properties of routing on the global Internet.
>   Because the scaling of routing is very tightly coupled to the way
>   that addresses are used, deployment of CIDR had implications for the
>   way in which addresses were assigned.
>
> 3.1  Aggregation efficiency and limitations
>
>   The only commonly-understood method for reducing routing state on a
>   packet-switched network is through aggregation of information.  For
>   CIDR to succeed in reducing the size and growth rate of the global
>   routing system, the IPv4 address assignment process needed to be
>   changed to make possible the aggregation of routing information along
>   topological lines.  Since, in general, the topology of the network is
>   determined by the service providers who have built it, topologically-
>   significant address assignments are necessarily service-provider
>   oriented.
>
>   Aggregation is simple for an end site which is connected to one
>   service provider: it uses address space assigned by its service
>   provider and that address space is a small piece of a larger block
>   allocated to the service provider.  No explicit route is needed for
>   the end site - the service provider advertises a single aggregate
>   route for the larger block; this advertisement provides reachability
>   and routeability for all of the customers numbered in the block.
>
>   There are two, more complex, situations that reduce the effectiveness
>   of aggregation:
>
>
>
>
> Fuller & Li             Expires October 10, 2005                [Page 7]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   o  An organization which is multi-homed.  Because a multi-homed
>      organization must be advertised into the system by each of its
>      service providers, it is often not feasible to aggregate its
>      routing information into the address space of any one of those
>      providers.  Note that the organization still may receive its
>      address assignment out of a service provider's address space
>      (which has other advantages), but a route to the organization's
>      prefix must still be explicitly advertised by all of its service
>      providers.  For this reason, the global routing cost for a multi-
>      homed organization is generally the same as it was prior to the
>      adoption of CIDR.
>
>   o  An organization which changes service provider but does not
>      renumber.  This has the effect of "punching a hole" in one of the
>      original service provider's aggregated route advertisements.  CIDR
>      handles this situation by requiring the newer service provider to
>      advertise a specific advertisement for the re-homed organization;
>      this advertisement is preferred over provider aggregates because
>      it is a longer match.  To maintain efficiency of aggregation, it
>      is recommended that an organization which changes service
>      providers plan to eventually migrate its network into a an prefix
>      assigned from its new provider's address space.  To this end, it
>      is recommended that mechanisms to facilitate such migration, such
>      as dynamic host address assignment using [RFC2131]) be deployed
>      wherever possible, and that additional protocol work be done to
>      develop improved technology for renumbering.
>
>   Note that some aggregation efficiency gain can still be had for
>   multi-homed sites (and, in general, for any site composed of
>   multiple, logical IPv4 networks) - by allocating a contiguous power-
>   of-two block address space to the site (as opposed to multiple,
>   independent prefixes) the site's routing information may be
>   aggregated into a single prefix.  Also, since the routing cost
>   associated with assigning a multi-homed site out of a service
>   provider's address space is no greater than the old method of
>   sequential number assignment by a central authority, it makes sense
>   to assign all end-site address space out of blocks allocated to
>   service providers.
>
>   It is also worthwhile to mention that since aggregation may occur at
>   multiple levels in the system, it may still be possible to aggregate
>   these anomalous routes at higher levels of whatever hierarchy may be
>   present.  For example, if a site is multi-homed to two relatively
>   small providers that both obtain connectivity and address space from
>   the same large provider, then aggregation by the large provider of
>   routes from the smaller networks will include all routes to the
>   multi-homed site.  The feasibility of this sort of second-level
>   aggregation depends on whether topological hierarchy exists between a
>
>
>
> Fuller & Li             Expires October 10, 2005                [Page 8]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   site, its directly-connected providers, and other providers to which
>   they are connected; it may be practical in some regions of the global
>   Internet but not in others.
>
>   Note: in the discussion and examples which follow, prefix notation is
>   used to represent routing destinations.  This is used for
>   illustration only and does not require that routing protocols use
>   this representation in their updates.
>
> 3.2  Distributed assignment of address space
>
>   In the early days of the Internet, IPv4 address space assignment was
>   performed by the central Network Information Center (NIC).  Class
>   A/B/C network numbers were assigned in essentially arbitrary order,
>   roughly according to the size of the organizations that requested
>   them.  All assignments were recorded centrally and no attempt was
>   made to assign network numbers in a manner that would allow routing
>   aggregation.
>
>   When CIDR was originally deployed, the central assignment authority
>   continued to exist but changed its procedures to assign large blocks
>   of "Class C" network numbers to each service provider.  Each service
>   provider, in turn, assigned bitmask-oriented subsets of the
>   provider's address space to each customer.  This worked reasonably
>   well as long as the number of service providers was relatively small
>   and relatively constant but did not scale well as the number of
>   service providers grew at a rapid rate.
>
>   As the Internet started to expand rapidly in the 1990s, it became
>   clear that a single, centralized address assignment authority was
>   problematic.  This function began being de-centralized when address
>   space assignment for European Internet sites was delegated in bit-
>   aligned blocks of 16777216 addresses (what CIDR would later define as
>   a /8) to the RIPE NCC ([RIPE]), effectively making it the first of
>   the RIRs.  Since then, address assignment has been formally
>   distributed as a hierarchical function with IANA, the RIRs, and the
>   service providers.  Removing the bottleneck of a single organization
>   having responsibility for the global Internet address space greatly
>   improved the efficiency and response time for new assignments.
>
>   Hierarchical delegation of addresses in this manner implies that
>   sites with addresses assigned out of a given service provider are,
>   for routing purposes, part of that service provider and will be
>   routed via its infrastructure.  This implies that routing information
>   about multi-homed organizations, i.e., organizations connected to
>   more than one network service provider, will still need to be known
>   by higher levels in the hierarchy.
>
>
>
>
> Fuller & Li             Expires October 10, 2005                [Page 9]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   Some of these issues are discussed at greater length in [RFC1518].
>
> 4.  Routing implementation considerations
>
>   With the change from classful network numbers to classless prefixes,
>   it is not possible to infer the network mask from the initial bit
>   pattern of an IPv4 address.  This has implications for how routing
>   information is stored and propagated.  Network masks or prefix
>   lengths must be explicitly carried in routing protocols.  Interior
>   routing protocols such as OSPF [RFC2178], IS-IS [RFC1195], RIPv2
>   [RFC2453], and Cisco EIGRP, and the BGP4 exterior routing protocol
>   [RFC1771] all support this functionality, having been developed or
>   modified as part of the deployment of classless inter-domain routing
>   during the 1990s.
>
>   Older interior routing protocols, such as RIP [RFC1058], HELLO, and
>   Cisco IGRP, and older exterior routing protocols, such as EGP
>   [RFC904], do not support explicit carriage of prefix length/mask and
>   thus cannot be effectively used on the Internet in other than very
>   limited, stub configurations.  While their use may be appropriate in
>   simple, legacy end-site configurations, they are considered obsolete
>   and should NOT be used in transit networks connected to the global
>   Internet.
>
>   Similarly, routing and forwarding tables in layer-3 network equipment
>   must be organized to store both prefix and prefix length or mask.
>   Equipment which organizes its routing/forwarding information
>   according to legacy class A/B/C network/subnet conventions cannot be
>   expected to work correctly on networks connected to the global
>   Internet; use of such equipment is not recommended.  Fortunately,
>   very little such equipment is in use today.
>
> 4.1  Rules for route advertisement
>
>   1.  Routing to all destinations must be done on a longest-match basis
>       only.  This implies that destinations which are multi-homed
>       relative to a routing domain must always be explicitly announced
>       into that routing domain - they cannot be summarized (this makes
>       intuitive sense - if a network is multi-homed, all of its paths
>       into a routing domain which is "higher" in the hierarchy of
>       networks must be known to the "higher" network).
>
>   2.  A router which generates an aggregate route for multiple, more-
>       specific routes must discard packets which match the aggregate
>       route but not any of the more-specific routes.  In other words,
>       the "next hop" for the aggregate route should be the null
>       destination.  This is necessary to prevent forwarding loops when
>       some addresses covered by the aggregate are not reachable.
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 10]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   Note that during failures, partial routing of traffic to a site which
>   takes its address space from one service provider but which is
>   actually reachable only through another (i.e., the case of a site
>   which has changed service providers) may occur because such traffic
>   will be forwarded along the path advertised by the aggregated route.
>   Rule #2 will prevent packet mis-delivery by causing such traffic to
>   be discarded by the advertiser of the aggregated route, but the
>   output of "traceroute" and other similar tools will suggest that a
>   problem exists within that network rather than in the network which
>   is no longer advertising the more-specific prefix.  This may be
>   confusing to those trying to diagnose connectivity problems; see the
>   example in Section 5.2 for details.  A solution to this perceived
>   "problem" is beyond the scope of this document - it lies with better
>   education of the user/operator community, not in routing technology.
>
>   An implementation following these rules should also be generalized,
>   so that an arbitrary network number and mask are accepted for all
>   routing destinations.  The only outstanding constraint is that the
>   mask must be left contiguous.  Note that the degenerate route to
>   prefix 0.0.0.0/0 is used as a default route and MUST be accepted by
>   all implementations.  Further, to protect against accidental
>   advertisements of this route via the inter-domain protocol, this
>   route should only be advertised when a router is explicitly
>   configured to do so - never as a non-configured, "default" option.
>
> 4.2  How the rules work
>
>   Rule #1 guarantees that the routing algorithm used is consistent
>   across implementations and consistent with other routing protocols,
>   such as OSPF.  Multi-homed networks are always explicitly advertised
>   by every service provider through which they are routed even if they
>   are a specific subset of one service provider's aggregate (if they
>   are not, they clearly must be explicitly advertised).  It may seem as
>   if the "primary" service provider could advertise the multi-homed
>   site implicitly as part of its aggregate, but the assumption that
>   longest-match routing is always done causes this not to work.
>
>   Rule #2 guarantees that no routing loops form due to aggregation.
>   Consider a site that has been assigned 192.168.64/19 by its "parent"
>   provider that has 192.168.0.0/16.  The "parent" network will
>   advertise 192.168.0.0/16 to the "child" network.  If the "child"
>   network were to lose internal connectivity to 192.168.65.0/24 (which
>   is part of its aggregate), traffic from the "parent" to the to the
>   "child" destined for 192.168.65.1 will follow the "child's"
>   advertised route.  When that traffic gets to the "child", however,
>   the mid-level *must not* follow the route 192.168.0.0/16 back up to
>   the "parent", since that would result in a forwarding loop.  Rule #2
>   says that the "child" may not follow a less-specific route for a
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 11]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   destination which matches one of its own aggregated routes
>   (typically, this is implemented by installing a "discard" or "null"
>   route for all aggregated prefixes which one network advertises to
>   another).  Note that handling of the "default" route (0.0.0.0/0) is a
>   special case of this rule - a network must not follow the default to
>   destinations which are part of one of it's aggregated advertisements.
>
> 4.3  A note on prefix filter formats
>
>   Systems which process route announcements must be able to verify that
>   information which they receive is acceptable according to policy
>   rules.  Implementations which filter route advertisements must allow
>   masks or prefix lengths in filter elements.  Thus, filter elements
>   which formerly were specified as:
>
>           accept 172.16.0.0
>           accept 172.25.120.0.0
>           accept 172.31.0.0
>           deny 10.2.0.0
>           accept 10.0.0.0
>
>   now look something like:
>
>           accept 172.16.0.0/16
>           accept 172.25.0.0/16
>           accept 172.31.0.0/16
>           deny 10.2.0.0/16
>           accept 10.0.0.0/8
>
>   This is merely making explicit the network mask which was implied by
>   the class A/B/C classification of network numbers.  It is also useful
>   to enhance filtering capability to allow the match of a prefix and
>   all more-specific prefixes with the same bit pattern; fortunately,
>   this functionality has been implemented by most vendors of equipment
>   used on the Internet.
>
> 4.4  Responsibility for and configuration of aggregation
>
>   Under normal circumstances, a routing domain (or "Autonomous System")
>   which has been allocated or assigned a set of prefixes has sole
>   responsibility for aggregation of those prefixes.  In the usual case,
>   the AS will install configuration in one or more of its routers to
>   generate aggregate routes based on more-specific routes known to its
>   internal routing system; these aggregate routes are advertised into
>   the global routing system by the border routers for the routing
>   domain.  The more-specific internal routes which overlap with the
>   aggregate routes should not be advertised globally.  In some cases,
>   an AS may wish to delegate aggregation responsibility to another AS
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 12]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   (for example, a customer may wish for its service provider to
>   generate aggregated routing information on its behalf); in such
>   cases, aggregation is performed by a router in the second AS based on
>   the routes that it receives from the first combined with configured
>   policy information describing how those routes should be aggregated.
>
>   It should be mentioned that one provider may choose to perform
>   aggregation on the routes it receives from another without explicit
>   agreement; this is termed "proxy aggregation".  This can be a useful
>   tool for reducing the amount of routing state that an AS must carry
>   and propagate to its customers and neighbors, proxy aggregation can
>   also create inconsistencies in global routing state.  Consider what
>   happens if both AS 2 and 3 receive routes from AS 1 but AS 2 performs
>   proxy aggregation while AS 3 does not.  Other AS's which receive
>   transit routing information from both AS 2 and AS 3 will see an
>   inconsistent view of the routing information originated by AS 1.
>   This may cause an unexpected shift of traffic toward AS 1 through AS
>   3 for AS 3's customers and any others receiving transit routes from
>   AS 3.  Because proxy aggregation can cause unanticipated consequences
>   for parts of the Internet that have no relationship with either the
>   source of the aggregated routes or the party providing aggregation,
>   it should be used with extreme caution.
>
>   Configuration of the routes to be combined into aggregates is an
>   implementation of routing policy and does require some manually-
>   maintained information.  As an addition to the information that must
>   be maintained for a set of routeable prefixes, aggregation
>   configuration is typically just a line or two defining the range of
>   the block of IPv4 addresses to aggregate.  A site performing its own
>   aggregation is doing so for address blocks that it has been assigned;
>   a site performing aggregation on behalf of another knows this
>   information based on an agreement to delegate aggregation.  Assuming
>   a best common practice for network administrators to exchange lists
>   of prefixes to accept from one and other, configuration of
>   aggregation information does not introduce significant additional
>   administrative overhead.
>
>   The generation of an aggregate route is usually specified either
>   statically or in response to learning an active dynamic route for a
>   prefix contained within the aggregate route.  If such dynamic
>   aggregate route advertisement is done, care should be taken that
>   routes are not excessively added or withdrawn (known as "route
>   flapping"); in general, a dynamic aggregate route advertisement is
>   added when at least one component of the aggregate becomes reachable
>   and it is withdrawn only when all components become unreachable.
>   Properly configured, aggregated routes are more stable than non-
>   aggregated routes and thus improve global routing stability.
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 13]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   Implementation note: aggregation of the "Class D" (multicast) address
>   space is beyond the scope of this document.
>
> 4.5  Route propagation and routing protocol considerations
>
>   Prior to the original deployment of CIDR, common practice was to
>   propagate routes learned via exterior routing protocols (i.e.  EGP or
>   BGP) through a site's interior routing protocol (typically, OSPF,
>   IS-IS, or RIP).  This was done to ensure that consistent and correct
>   exit points were chosen for traffic destined to a destination learned
>   through those protocols.  Four evolutionary effects -- the advent of
>   CIDR, explosive growth of global routing state, widespread adoption
>   of BGP4, and a requirement to propagate full path information -- have
>   combined to deprecate that practice.  To ensure proper path
>   propagation and prevent inter-AS routing inconsistency (BGP4's loop
>   detection/prevention mechanism requires full path propagation),
>   transit networks must use internal BGP (iBGP) for carrying routes
>   learned from other providers both within and through their networks.
>
> 5.  Example of new address assignments and routing
>
> 5.1  Address delegation
>
>   Consider the block of 524288 (2^19) addresses beginning with
>   10.24.0.0 and ending with 10.31.255.255 allocated to a single network
>   provider, "PA".  This is equivalent in size to a block of 2048 legacy
>   "class C" network numbers (or /24s).  A classless route to this block
>   would be described as 10.24.0.0 with mask of 255.248.0.0 the prefix
>   10.24.0.0/13.
>
>   Assume this service provider connects six sites in the following
>   order (significant because it demonstrates how temporary "holes" may
>   form in the service provider's address space):
>
>   o  "C1" requiring fewer than 2048 addresses (/21 or 8 x /24)
>
>   o  "C2" requiring fewer than 4096 addresses (/20 or 16 x /24)
>
>   o  "C3" requiring fewer than 1024 addresses (/22 or 4 x /24)
>
>   o  "C4" requiring fewer than 1024 addresses (/22 or 4 x /24)
>
>   o  "C5" requiring fewer than 512 addresses (/23 or 2 x /24)
>
>   o  "C6" requiring fewer than 512 addresses (/23 or 2 x /24)
>
>   In all cases, the number of IPv4 addresses "required" by each site is
>   assumed to allow for significant growth.  The service provider
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 14]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   delegates its address space as follows:
>
>   o  C1: assign 10.24.0 through 10.24.7.  This block of networks is
>      described by the route 10.24.0.0/21 (mask 255.255.248.0)
>
>   o  C2: assign 10.24.16 through 10.24.31.  This block is described by
>      the route 10.24.16.0/20 (mask 255.255.240.0)
>
>   o  C3: assign 10.24.8 through 10.24.11.  This block is described by
>      the route 10.24.8.0/22 (mask 255.255.252.0)
>
>   o  C4: assign 10.24.12 through 10.24.15.  This block is described by
>      the route 10.24.12.0/22 (mask 255.255.252.0)
>
>   o  C5: assign 10.24.32 and 10.24.33.  This block is described by the
>      route 10.24.32.0/23 (mask 255.255.254.0)
>
>   o  C6: assign 10.24.34 and 10.24.35.  This block is described by the
>      route 10.24.34.0/23 (mask 255.255.254.0)
>
>   These six sites should be represented as six prefixes of varying size
>   within the provider IGP.  If, for some reason, the provider were to
>   use an obsolete IGP that doesn't support classless routing or
>   variable-length subnets, then then explicit routes all /24s will have
>   to be carried.
>
>   To make this example more realistic, assume that C4 and C5 are multi-
>   homed through some other service provider, "PB".  Further assume the
>   existence of a site "C7" which was originally connected to "RB" but
>   has moved to "PA".  For this reason, it has a block of network
>   numbers which are assigned out "PB"'s block of (the next) 2048 x /24.
>
>   o  C7: assign 10.32.0 through 10.32.15.  This block is described by
>      the route 10.32.0.0/20 (mask 255.255.240.0)
>
>   For the multi-homed sites, assume that C4 is advertised as primary
>   via "RA" and secondary via "RB"; C5 is primary via "RB" and secondary
>   via "RA".  In addition, assume that "RA" and "RB" are both connected
>   to the same transit service provider "BB".
>
>   Graphically, this topology looks something like this:
>
>
>
>
>
>
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 15]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   10.24.0.0 -- 10.24.7.0__         __10.32.0.0 - 10.32.15.0
>   C1: 10.24.0.0/21        \       /  C7: 10.32.0.0/20
>                            \     /
>                             +----+                              +----+
>   10.24.16.0 - 10.24.31.0_  |    |                              |    |
>   C2: 10.24.16.0/20       \ |    |  _10.24.12.0 - 10.24.15.0__  |    |
>                            \|    | / C4: 10.24.12.0/20        \ |    |
>                             |    |/                            \|    |
>   10.24.8.0 - 10.24.11.0___/| PA |\                             | PB |
>   C3: 10.24.8.0/22          |    | \__10.24.32.0 - 10.24.33.0___|    |
>                             |    |    C5: 10.24.32.0/23         |    |
>                             |    |                              |    |
>   10.24.34.0 - 10.24.35.0__/|    |                              |    |
>   C6: 10.24.34.0/23         |    |                              |    |
>                             +----+                              +----+
>                               ||                                  ||
>   routing advertisements:     ||                                  ||
>                               ||                                  ||
>           10.24.12.0/22 (C4)  ||              10.24.12.0/22 (C4)  ||
>           10.32.0.0/20 (C7)   ||              10.24.32.0/23 (C5)  ||
>           10.24.0.0/13 (PA)   ||              10.32.0.0/13 (PB)   ||
>                               ||                                  ||
>                               VV                                  VV
>                            +---------- BACKBONE NETWORK BB ----------+
>
>
> 5.2  Routing advertisements
>
>   To follow rule #1, PA will need to advertise the block of addresses
>   that it was given and C7.  Since C4 is multi-homed and primary
>   through PA, it must also be advertised.  C5 is multi-homed and
>   primary through PB.  In principal (and in the example above), it need
>   not be advertised since longest match by PB will automatically select
>   PB as primary and the advertisement of PA's aggregate will be used as
>   a secondary.  In actual practice, C5 will normally be advertised via
>   both providers.
>
>   Advertisements from "PA" to "BB" will be:
>
>          10.24.12.0/22 primary    (advertises C4)
>          10.32.0.0/20 primary     (advertises C7)
>          10.24.0.0/13 primary     (advertises remainder of PA)
>
>   For PB, the advertisements must also include C4 and C5 as well as
>   it's block of addresses.
>
>   Advertisements from "PB" to "BB" will be:
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 16]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>          10.24.12.0/22 secondary  (advertises C4)
>          10.24.32.0/23 primary    (advertises C5)
>          10.32.0.0/13 primary     (advertises remainder of RB)
>
>   To illustrate the problem diagnosis issue mentioned in Section 4.1,
>   consider what happens if PA loses connectivity to C7 (the site which
>   is assigned out of PB's space).  In a stateful protocol, PA will
>   announce to BB that 10.32.0.0/20 has become unreachable.  Now, when
>   BB flushes this information out of its routing table, any future
>   traffic sent through it for this destination will be forwarded to PB
>   (where it will be dropped according to Rule #2) by virtue of PB's
>   less specific match 10.32.0.0/13.  While this does not cause an
>   operational problem (C7 is unreachable in any case), it does create
>   some extra traffic across "BB" (and may also prove confusing to
>   someone trying to debug the outage with "traceroute").  A mechanism
>   to cache such unreachable state might be nice but is beyond the scope
>   of this document.
>
> 6.  Domain Name Service considerations
>
>   One aspect of Internet services which was notably affected by the
>   move to CIDR was the mechanism used for address-to-name translation:
>   the IN-ADDR.ARPA zone of the domain system.  Because this zone is
>   delegated on octet boundaries only, the move to an address assignment
>   plan which uses bitmask-oriented addressing caused some increase in
>   work for those who maintain parts of the IN-ADDR.ARPA zone.
>
>   As described above, the IN-ADDR.ARPA zone is necessarily organized
>   along octet boundaries.  Prior to the adoption of CIDR, IN-ADDR.ARPA
>   was also constrained such that delegations were only permitted along
>   legacy, class A/B/C network number boundaries.  This created a
>   difficult situation for more flexible, CIDR prefixes.  Consider a
>   hypothetical large network provider named "BigNet" which has been
>   allocated the block 10.4.0.0 through 10.7.255.0 (the CIDR prefix
>   10.4.0.0/14).  Under the old delegation policies, the top-level IN-
>   ADDR.ARPA domain servers would need to have 1024 entries of the form:
>
>       0.4.10.IN-ADDR.ARPA.   IN      NS      NS1.BIG.NET.
>
>       1.4.10.IN-ADDR.ARPA.   IN      NS      NS1.BIG.NET.
>
>               ....
>
>       255.7.10.IN-ADDR.ARPA. IN      NS      NS1.BIG.NET.
>
>   By revising the policy as described above, this was reduced to four
>   delegation records:
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 17]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>       4.10.IN-ADDR.ARPA.     IN      NS      NS1.BIG.NET.
>
>       5.10.IN-ADDR.ARPA.     IN      NS      NS1.BIG.NET.
>
>       6.10.IN-ADDR.ARPA.     IN      NS      NS1.BIG.NET.
>
>       7.10.IN-ADDR.ARPA.     IN      NS      NS1.BIG.NET.
>
>   The provider then maintains further delegations of naming authority
>   for each individual /24 which it assigns, rather than having each
>   registered separately.  Note that due to the way the DNS is designed,
>   it is still possible for the top-level IN-ADDR.ARPA name servers to
>   maintain the delegation information for individual networks for which
>   the provider is unwilling or unable to do so.  The example above
>   illustrates only the records for a single name server.  In the normal
>   case, there are usually several name servers for each domain, thus
>   the size of the examples will double or triple in the common cases.
>
>   For BIG.NET to assign a blocks smaller than /24 to its customers, it
>   can similarly delegate DNS authority for those addresses.  For
>   example, if it were to assign 10.4.99.64/26 to its customer
>   CUSTONE.COM and 10.4.99.128/27 to its customer CUSTTWO.COM, it could
>   add the following records to delegate DNS for the addresses to those
>   customers:
>
>       64.99.4.10.IN-ADDR.ARPA.    IN    NS    NS1.CUSTONE.COM.
>
>       65.99.4.10.IN-ADDR.ARPA.    IN    NS    NS1.CUSTONE.COM.
>
>              ....
>
>       127.99.4.10.IN-ADDR.ARPA.   IN    NS    NS1.CUSTONE.COM
>
>       128.99.4.10.IN-ADDR.ARPA.   IN    NS    NS1.CUSTTWO.COM
>
>       129.99.4.10.IN-ADDR.ARPA.   IN    NS    NS1.CUSTTWO.COM
>
>              ....
>
>       159.99.4.10.IN-ADDR.ARPA.   IN    NS    NS1.CUSTTWO.COM
>
>   And if BIG.NET also assigned 10.4.99.160/30 to CUSTTHREE.COM but this
>   customer did not want to run its own DNS, BIG.NET could provide that
>   service for the customer by installing the appropriate PTR records:
>
>
>
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 18]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>       160.99.4.10.IN-ADDR.ARPA.   IN    PTR   NET.CUSTTHREE.COM.
>
>       161.99.4.10.IN-ADDR.ARPA.   IN    PTR   HOST1.CUSTTHREE.COM.
>
>       162.99.4.10.IN-ADDR.ARPA.   IN    PTR   HOST2.CUSTTHREE.COM.
>
>       163.99.4.10.IN-ADDR.ARPA.   IN    PTR   BCAST.CUSTTHREE.COM.
>
>   See [RFC2317] for a much more detailed discussion of DNS delegation
>   with classless addressing.
>
> 7.  Transition to a long term solution
>
>   CIDR was designed to be a short-term solution to the problems of
>   routing state and address depletion on the IPv4 Internet.  It does
>   not change the fundamental Internet routing or addressing
>   architectures.  It is not expected to affect any plans for transition
>   to a more long-term solution except, perhaps, by delaying the urgency
>   of developing such a solution.
>
> 8.  Analysis of CIDR's effect on global routing state
>
>   When CIDR was first proposed in the early 1990s, the original authors
>   made some observations about the growth rate of global routing state
>   and offered projections on how CIDR deployment would, hopefully,
>   reduce what appeared to be exponential growth to a more sustainable
>   rate.  Since that deployment, an ongoing effort, called "The CIDR
>   Report" [CRPT] has attempted to quantify and track that growth rate.
>   What follows is a brief summary of the CIDR report as of March, 2005,
>   with an attempt to explain the various patterns of and change in
>   growth rate that have occurred since measurements of the size of
>   global routing state began in 1988.
>
>   Examining the graph of "Active BGP Table Entries" [CBGP] there appear
>   to be several different growth trends with distinct inflection points
>   reflecting changes in policy and practice.  The trends and events
>   which are believed to have caused them were:
>
>   1.  Exponential growth at the far left of the graph.  This represents
>       the period of early expansion and commercialization of the former
>       research network, from the late 1980s through approximately 1994.
>       The major driver for this growth was a lack of aggregation
>       capability for transit providers, and the widespread use of
>       legacy Class C allocations for end sites.  Each time a new site
>       was connected to the global Internet, one or more new routing
>       entries were generated.
>
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 19]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   2.  Acceleration of the exponential trend in late 1993 and early 1994
>       as CIDR supernet" blocks were first assigned by the NIC and
>       routed as separate legacy class-C networks by service provider.
>
>   3.  A sharp drop in 1994 as BGP4 deployment by providers allowed
>       aggregation of the "supernet" blocks.  Note that the periods of
>       largest declines in the number of routing table entries typically
>       correspond to the weeks following each meeting of the IETF CIDR
>       Deployment Working Group.
>
>   4.  Roughly linear growth from mid-1994 to early 1999 as CIDR-based
>       address assignments were made and aggregated routes added
>       throughout the network.
>
>   5.  A new period of exponential growth again from early 1999 until
>       2001 as the "high-tech bubble" fueled both rapid expansion of
>       Internet as well as a large increase in more-specific route
>       advertisements for multi-homing and traffic engineering.
>
>   6.  Flattening of growth through 2001 caused by a combination of the
>       "dot-com bust", which caused many organizations to cease
>       operations, and the "CIDR police" [CPOL] work aimed at improving
>       aggregation efficiency.
>
>   7.  Roughly linear growth through 2002 and 2003.  This most likely
>       represents a resumption of the "normal" growth rate observed
>       before the "bubble" as well as an end to the "CIDR Police"
>       effort.
>
>   8.  A more recent trend of exponential growth beginning in 2004.  The
>       best explanation would seem to be an improvement of the global
>       economy driving increased expansion of the Internet and the
>       continued absence of the "CIDR Police" effort, which previously
>       served as an educational tool for new providers to improve
>       aggregation efficiency.  There have also been some cases where
>       service providers have deliberately de-aggregated prefixes in an
>       attempt to mitigate security problems caused by conflicting route
>       advertisements (see Section 10).  While this behavior may solve
>       the short-term problems seen by such providers, it is
>       fundamentally non-scalable and quite detrimental to the community
>       as a whole.  In addition, there appear to be many providers
>       advertising both their allocated prefixes and all of the /24
>       components of them, probably due to a lack of consistent current
>       information about recommended routing configuration.
>
>
>
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 20]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
> 9.  Conclusions and Recommendations
>
>   In 1992, when CIDR was first developed, there were serious problems
>   facing the continued growth of the Internet.  Growth in routing state
>   complexity, and the rapid increase in consumption of address space
>   made it appear that one or both problems would preclude continued
>   growth of the Internet within a few short years.
>
>   Deployment of CIDR, in combination with BGP4's support for carrying
>   classless prefix routes, alleviated the short-term crisis.  It was
>   only through a concerted effort by both the equipment manufacturers
>   and the provider community that this was achieved.  The threat (and,
>   perhaps in some cases, actual implementation of) charging networks
>   for advertising prefixes may have offered an additional incentive to
>   share the address space, and hence the associated costs of
>   advertising routes to service providers.
>
>   The IPv4 routing system architecture carries topology information
>   based on aggregate address advertisements and a collection of more-
>   specific advertisements that are associated with traffic engineering,
>   multi-homing and local configuration.  As of March, 2005, the base
>   aggregate address load in the routing system has some 75,000 entries.
>   Approximately 85,000 additional entries are more specific entries of
>   this base "root" collection.  There is reason to believe that many of
>   these additional entries are exist to solve problems of regional or
>   even local scope and should not need to be globally propagated.
>
>   An obvious question to ask is whether CIDR can continue to be a
>   viable approach to keeping global routing state growth and address
>   space depletion at sustainable rates.  Recent measurements indicate
>   that exponential growth has resumed but further analysis suggests
>   that this trend can be mitigated by a more active effort to educate
>   service providers on efficient aggregation strategies and proper
>   equipment configuration.  Looking farther forward, there is a clear
>   need for better multi-homing technology that does not require global
>   routing state for each site and for methods of performing traffic
>   load balancing that do not require adding even more state.  Without
>   such developments and in the absence of major architectural change,
>   aggregation is the only tool available for making routing scale in
>   the global Internet.
>
> 10.  Security Considerations
>
>   The introduction of routing protocols which support classless
>   prefixes and a move to a forwarding model that mandates that more-
>   specific (longest-match) routes be preferred when they overlap with
>   routes to less-specific prefixes introduces at least two security
>   concerns:
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 21]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>      Traffic can be hijacked by advertising a prefix for a given
>      destination that is more specific than the aggregate that is
>      normally advertised for that destination.  For example, assume a
>      popular end system with address 192.168.17.100 that is connected
>      to a service provider that advertises 192.168.16.0/20.  A
>      malicious network operator interested in intercepting traffic for
>      this site might advertise, or at least attempt to advertise,
>      192.168.17.0/24 into the global routing system.  Because this
>      prefix is more-specific than the "normal" prefix, traffic will be
>      diverted away from the legitimate end system and to the network
>      owned by the malicious operator.  Prior to the advent of CIDR, it
>      was possible to induce traffic from some parts of the network to
>      follow a false advertisement that exactly matched a particular
>      network number; CIDR makes this problem somewhat worse, since
>      longest-match routing generally causes all traffic to prefer more-
>      specific routes over less-specific routes.  The remedy for the
>      CIDR-based attack, though, is the same as for a pre-CIDR-based
>      attack: establishment of trust relationships between providers,
>      coupled with and strong route policy filters at provider borders.
>      Unfortunately, the implementation of such filters is difficult in
>      the highly de-centralized Internet.  As a workaround, many
>      providers do implement generic filters that set upper bounds,
>      derived from RIR guidelines for the sizes of blocks that they
>      allocate, on the lengths of prefixes that are accepted from other
>      providers.  It is worth noting that "spammers" have been observed
>      using this sort of attack to temporarily hijack address space in
>      order to hide the origin of the traffic ("spam" email messages)
>      that they generate.
>
>      Denial-of-service attacks can be launched against many parts of
>      the Internet infrastructure by advertising a large number of
>      routes into the system.  Such an attack is intended to cause
>      router failures by overflowing routing and forwarding tables.  A
>      good example of a non-malicious incident which caused this sort of
>      failure was the infamous "AS 7007" event [7007] where a router
>      mis-configuration by an operator caused a huge number of invalid
>      routes to be propagated through the global routing system.  Again,
>      this sort of attack is not really new with CIDR; using legacy
>      class A/B/C routes, it was possible to advertise a maximum of
>      16843008 unique network numbers into the global routing system, a
>      number which is sufficient to cause problems for even the most
>      modern routing equipment made in 2005.  What is different is that
>      the moderate complexity of correctly configuring routers in the
>      presence of CIDR does tend to make accidental "attacks" of this
>      sort more likely.  Measures to prevent this sort of attack are
>      much the same as those described above for the hijacking, with the
>      addition that best common practice is to also configure a
>      reasonable maximum number of prefixes that a border router will
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 22]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>      accept from its neighbors.
>
>      Note that this is not intended to be an exhaustive analysis of the
>      sorts of attacks that CIDR makes easier; a more comprehensive
>      analysis of security vulnerabilities in the global routing system
>      is beyond the scope of this document.
>
>
> 11.  Acknowledgments
>
>   The authors wish to express appreciation to the other original
>   authors of RFC1519 (Kannan Varadhan, Jessica Yu), to the ROAD group
>   with whom many of the ideas behind CIDR were inspired and developed,
>   and to the early reviewers of this re-spun version of the document
>   (Barry Greene, Geoff Huston, Danny McPherson, Dave Meyer, Eliot Lear,
>   Bill Norton, Ted Seely, Philip Smith) whose comments, corrections,
>   and suggestions were invaluable.
>
> 12.  References
>
> 12.1  Normative References
>
>   [RFC791]  Postel, J., "Internet Protocol", RFC 791, September 1981.
>
> 12.2  Informative References
>
>   [RFC1338]  Fuller, V., Li, T., Varadhan, K., and J. Yu,
>              "Supernetting: an Address Assignment and Aggregation
>              Strategy", RFC 1338, June 1992.
>
>   [RFC1519]  Fuller, V., Li, T., Varadhan, K., and J. Yu, "Classless
>              Inter-Domain Routing: an Address Assignment and
>              Aggregation Strategy", RFC 1519, September 1993.
>
>   [IANA]     "Internet Assigned Numbers Authority",
>              <http://www.iana.org>.
>
>   [NRO]      "Number Resource Organization", <http://www.nro.net>.
>
>   [RFC1380]  Gross, P. and P. Almquist, "IESG Deliberations on Routing
>              and Addressing", RFC 1380, November 1992.
>
>   [LWRD]     "The Long and Winding Road",
>              <http://rms46.vlsm.org/1/42.html>.
>
>   [RFC2178]  Moy, J., "The OSPF Specification Version 2", RFC 2178,
>              July 1997.
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 23]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
>   [RFC1195]  Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
>              dual environments", RFC 1195, December 1990.
>
>   [RFC2453]  Malkin, G., "RIP Version 2", RFC 2453, November 1998.
>
>   [RFC1771]  Rekhter, Y. and T. Li, "A Border Gateway Protocol 4
>              (BGP-4)", RFC 1771, March 1995.
>
>   [RFC1058]  Hedrick, C., "Routing Information Protocol", RFC 1058,
>              June 1988.
>
>   [RFC904]   Mills, D., "Exterior Gateway Protocol formal
>              specification", RFC 904, April 1984.
>
>   [RFC3021]  Retana, A., White, R., Fuller, V., and D. McPherson,
>              "Using 31-Bit Prefixes on IPv4 Point-to-Point Links",
>              RFC 3021, December 2000.
>
>   [RFC2131]  Droms, R., "Dynamic Host Configuration Protocol",
>              RFC 2131, March 1997.
>
>   [RIPE]     "RIPE Network Coordination Centre", <http://www.ripe.net>.
>
>   [RFC1518]  Rekhter, Y. and T. Li, "An Architecture for IP Address
>              Allocation with CIDR", RFC 1518, September 1993.
>
>   [RFC2317]  Eidnes, H., de Groot, G., and P. Vixie, "Classless IN-
>              ADDR.ARPA delegation", RFC 2317, March 1998.
>
>   [CRPT]     "The CIDR Report", <http://www.cidr-report.org/>.
>
>   [CBGP]     "Graph: Active BGP Table Entries, 1988 to Present",
>              <http://bgp.potaroo.net/as4637/>.
>
>   [CPOL]     "CIDR Police - Please Pull Over and Show Us Your BGP",
>              <http://www.nanog.org/mtg-0302/cidr.html>.
>
>   [7007]     "NANOG mailing list discussion of the "AS 7007" incident",
>              <http://www.merit.edu/mail.archives/nanog/1997-04/
>              msg00340.html>.
>
>
>
>
>
>
>
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 24]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
> Authors' Addresses
>
>   Vince Fuller
>   170 W. Tasman Drive
>   San Jose, CA  95134
>   USA
>
>   Email: vaf@cisco.com
>
>
>   Tony Li
>   170 W. Tasman Drive
>   San Jose, CA  95134
>   USA
>
>   Email: tli@cisco.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 25]
>
> Internet-Draft            CIDR Address Strategy               April 2005
>
>
> Intellectual Property Statement
>
>   The IETF takes no position regarding the validity or scope of any
>   Intellectual Property Rights or other rights that might be claimed to
>   pertain to the implementation or use of the technology described in
>   this document or the extent to which any license under such rights
>   might or might not be available; nor does it represent that it has
>   made any independent effort to identify any such rights.  Information
>   on the procedures with respect to rights in RFC documents can be
>   found in BCP 78 and BCP 79.
>
>   Copies of IPR disclosures made to the IETF Secretariat and any
>   assurances of licenses to be made available, or the result of an
>   attempt made to obtain a general license or permission for the use of
>   such proprietary rights by implementers or users of this
>   specification can be obtained from the IETF on-line IPR repository at
>   http://www.ietf.org/ipr.
>
>   The IETF invites any interested party to bring to its attention any
>   copyrights, patents or patent applications, or other proprietary
>   rights that may cover technology that may be required to implement
>   this standard.  Please address the information to the IETF at
>   ietf-ipr@ietf.org.
>
>
> Disclaimer of Validity
>
>   This document and the information contained herein are provided on an
>   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
>   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
>   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
>   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
>   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
>   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>
>
> Copyright Statement
>
>   Copyright (C) The Internet Society (2005).  This document is subject
>   to the rights, licenses and restrictions contained in BCP 78, and
>   except as set forth therein, the authors retain all their rights.
>
>
> Acknowledgment
>
>   Funding for the RFC Editor function is currently provided by the
>   Internet Society.
>
>
>
>
> Fuller & Li             Expires October 10, 2005               [Page 26]
> _________________________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
> web archive:        http://darkwing.uoregon.edu/~llynch/grow/
>

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr 12 12:55:22 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15379
	for <grow-archive@lists.ietf.org>; Tue, 12 Apr 2005 12:55:22 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CGrrSR000600;
	Tue, 12 Apr 2005 09:53:53 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3CGrrOG000598;
	Tue, 12 Apr 2005 09:53:53 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CGrqHF000504
	for <grow@lists.uoregon.edu>; Tue, 12 Apr 2005 09:53:52 -0700 (PDT)
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 12 Apr 2005 09:53:47 -0700
X-IronPort-AV: i="3.92,96,1112598000"; 
   d="scan'208"; a="248460638:sNHT60463000"
Received: from cisco.com (vaf-lnx1.cisco.com [171.71.140.59])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j3CGrgfI001936;
	Tue, 12 Apr 2005 09:53:42 -0700 (PDT)
Received: from vaf-lnx1.cisco.com (vaf-lnx1 [127.0.0.1])
	by cisco.com (8.12.11/8.12.11) with ESMTP id j3CGriPI006695;
	Tue, 12 Apr 2005 09:53:44 -0700
Received: (from vaf@localhost)
	by vaf-lnx1.cisco.com (8.12.11/8.12.11/Submit) id j3CGriAM006693;
	Tue, 12 Apr 2005 09:53:44 -0700
X-Authentication-Warning: vaf-lnx1.cisco.com: vaf set sender to vaf@cisco.com using -f
Date: Tue, 12 Apr 2005 09:53:44 -0700
From: Vince Fuller <vaf@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: grow@lists.uoregon.edu
Subject: Re: grow: draft of new RFC1519 replacement
Message-ID: <20050412165344.GA6652@vaf-lnx1.cisco.com>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504120957010.3431@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.61.0504120957010.3431@netcore.fi>
User-Agent: Mutt/1.4.1i
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

> RFC-editor's search finds 8 current documents which have "CIDR" in 
> their title.
> 
> Which ones does this obsolete?  (I'd hope as many as 
> possible.)
> 
> Which documents (apart fromt he CIDR ones) does this Update (if any)?

I thought that the "Abstract" covered this:

   This memo discusses the strategy for address assignment of the
   existing 32-bit IPv4 address space with a view toward conserving the
   address space and limiting the growth rate of global routing state.
   This document is intended as a replacement for the original CIDR spec
   [RFC1519] with changes made both to clarify the concepts it
   introduced and, after more than twelve years, to update the Internet
   community on the results of deploying the technology it described.

As I understand the RFC publication process, the RFC editor will add an
appropriate "Obsoletes:" header to the document when it becomes an RFC; I
don't think an Internet-Draft is supposed to use that header, at least not
according to my reading through the "xml2rfc" pre-processor.

	--Vince
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr 12 13:47:46 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19936
	for <grow-archive@lists.ietf.org>; Tue, 12 Apr 2005 13:47:45 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CHjS3u006814;
	Tue, 12 Apr 2005 10:45:28 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3CHjSce006812;
	Tue, 12 Apr 2005 10:45:28 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CHjQQ5006610
	for <grow@lists.uoregon.edu>; Tue, 12 Apr 2005 10:45:27 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j3CHjEw16585;
	Tue, 12 Apr 2005 20:45:14 +0300
Date: Tue, 12 Apr 2005 20:45:14 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Vince Fuller <vaf@cisco.com>
cc: grow@lists.uoregon.edu
Subject: Re: grow: draft of new RFC1519 replacement
In-Reply-To: <20050412165344.GA6652@vaf-lnx1.cisco.com>
Message-ID: <Pine.LNX.4.61.0504122040050.16404@netcore.fi>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com>
 <Pine.LNX.4.61.0504120957010.3431@netcore.fi> <20050412165344.GA6652@vaf-lnx1.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

On Tue, 12 Apr 2005, Vince Fuller wrote:
>> Which documents (apart fromt he CIDR ones) does this Update (if any)?
>
> I thought that the "Abstract" covered this:
>
>   This memo discusses the strategy for address assignment of the
>   existing 32-bit IPv4 address space with a view toward conserving the
>   address space and limiting the growth rate of global routing state.
>   This document is intended as a replacement for the original CIDR spec
>   [RFC1519] with changes made both to clarify the concepts it
>   introduced and, after more than twelve years, to update the Internet
>   community on the results of deploying the technology it described.
>
> As I understand the RFC publication process, the RFC editor will add an
> appropriate "Obsoletes:" header to the document when it becomes an RFC; I
> don't think an Internet-Draft is supposed to use that header, at least not
> according to my reading through the "xml2rfc" pre-processor.

I was afraid this was the case; so this means to obsolete only 
RFC1519.

However, there are other relevant RFCs (below). I think the current 
RFC could obsolete all of these, with little or not added text.  It 
certainly doesn't seem to make sense to produce a bis version of all 
of these.

This is most important for Proposed Standards (RFC1517, RFC1518). 
Basically all these documents could be made Historic, replacing them 
with just one spec (e.g., this one).



RFC1817
  CIDR and Classful Routing  Y. Rekhter August 1995 ASCII 
INFORMATIONAL

RFC1520
  Exchanging Routing Information Across Provider Boundaries in the CIDR 
Environment  Y. Rekhter, C. Topolcic September 1993 ASCII 
INFORMATIONAL

RFC1519
  Classless Inter-Domain Routing (CIDR): an Address Assignment and 
Aggregation Strategy  V. Fuller, T. Li, J. Yu, K. Varadhan September 
1993 ASCII Obsoletes RFC1338  PROPOSED STANDARD

RFC1518
  An Architecture for IP Address Allocation with CIDR  Y. Rekhter, T. 
Li September 1993 ASCII   PROPOSED STANDARD

RFC1517
  Applicability Statement for the Implementation of Classless 
Inter-Domain Routing (CIDR)  Internet Engineering Steering Group, R. 
Hinden September 1993 ASCII Errata  PROPOSED STANDARD

RFC1482
  Aggregation Support in the NSFNET Policy-Based Routing Database  M. 
Knopper, S. Richardson June 1993 ASCII   INFORMATIONAL

RFC1481
  IAB Recommendation for an Intermediate Strategy to Address the Issue 
of Scaling  C. Huitema July 1993 ASCII   INFORMATIONAL

RFC1467
  Status of CIDR Deployment in the Internet  C. Topolcic August 1993 
ASCII Obsoletes RFC1367  INFORMATIONAL

..................



btw, the following clarifies it a bit more.

s/This document is intended as a replacement for the original CIDR 
spec [RFC1519]/This document Obsoletes RFC 1519/

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr 12 14:42:14 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24013
	for <grow-archive@lists.ietf.org>; Tue, 12 Apr 2005 14:42:13 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CIbXcS009270;
	Tue, 12 Apr 2005 11:37:33 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3CIbXeo009258;
	Tue, 12 Apr 2005 11:37:33 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CIbWNM008803
	for <grow@lists.uoregon.edu>; Tue, 12 Apr 2005 11:37:32 -0700 (PDT)
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 12 Apr 2005 11:37:28 -0700
Received: from cisco.com (vaf-lnx1.cisco.com [171.71.140.59])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j3CIbP7T016005;
	Tue, 12 Apr 2005 11:37:26 -0700 (PDT)
Received: from vaf-lnx1.cisco.com (vaf-lnx1 [127.0.0.1])
	by cisco.com (8.12.11/8.12.11) with ESMTP id j3CIbPeh008619;
	Tue, 12 Apr 2005 11:37:25 -0700
Received: (from vaf@localhost)
	by vaf-lnx1.cisco.com (8.12.11/8.12.11/Submit) id j3CIbPhd008617;
	Tue, 12 Apr 2005 11:37:25 -0700
X-Authentication-Warning: vaf-lnx1.cisco.com: vaf set sender to vaf@cisco.com using -f
Date: Tue, 12 Apr 2005 11:37:25 -0700
From: Vince Fuller <vaf@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: grow@lists.uoregon.edu
Subject: Re: grow: draft of new RFC1519 replacement
Message-ID: <20050412183725.GA8539@vaf-lnx1.cisco.com>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504120957010.3431@netcore.fi> <20050412165344.GA6652@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504122040050.16404@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.61.0504122040050.16404@netcore.fi>
User-Agent: Mutt/1.4.1i
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

> I was afraid this was the case; so this means to obsolete only 
> RFC1519.
> 
> However, there are other relevant RFCs (below). I think the current 
> RFC could obsolete all of these, with little or not added text.  It 
> certainly doesn't seem to make sense to produce a bis version of all 
> of these.
> 
> This is most important for Proposed Standards (RFC1517, RFC1518). 
> Basically all these documents could be made Historic, replacing them 
> with just one spec (e.g., this one).

Hmm. I am very wary of expanding the scope of this document; the hope is that,
being simply an update and clarification of RFC1519, it will be fairly easy to
get through the standards process. The food-fight over RFC1519 and CIDRD was
pretty ugly; I don't think anybody wants to go through that again.

Do you really think that the new draft, as currently written, covers all of
the ground of 1467, 1481, 1482, 1517, 1518, 1520, and 1817? I can well believe
that many, if not most, of those documents should be re-classified as
"historical" as part of the NEWTRK effort but that seems beyond the
scope of the RFC1519-rewrite.

> btw, the following clarifies it a bit more.
> 
> s/This document is intended as a replacement for the original CIDR 
> spec [RFC1519]/This document Obsoletes RFC 1519/

I have changed the abstract to:

   This memo discusses the strategy for address assignment of the
   existing 32-bit IPv4 address space with a view toward conserving the
   address space and limiting the growth rate of global routing state.
   This document makes the original CIDR spec [RFC1519] obsolete, with
   changes made both to clarify the concepts it introduced and, after
   more than twelve years, to update the Internet community on the
   results of deploying the technology described.

How is that? While grammatically correct, using "obsolete" as a verb seems a
little awkward to me...

	--Vince
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr 12 15:04:18 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25794
	for <grow-archive@lists.ietf.org>; Tue, 12 Apr 2005 15:04:17 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CJ3DTo028501;
	Tue, 12 Apr 2005 12:03:14 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3CJ3Djs028500;
	Tue, 12 Apr 2005 12:03:13 -0700 (PDT)
Received: from netcore.fi (netcore.fi [193.94.160.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CJ3CdC028215
	for <grow@lists.uoregon.edu>; Tue, 12 Apr 2005 12:03:12 -0700 (PDT)
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id j3CJ2sv18288;
	Tue, 12 Apr 2005 22:02:54 +0300
Date: Tue, 12 Apr 2005 22:02:54 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Vince Fuller <vaf@cisco.com>
cc: grow@lists.uoregon.edu
Subject: Re: grow: draft of new RFC1519 replacement
In-Reply-To: <20050412183725.GA8539@vaf-lnx1.cisco.com>
Message-ID: <Pine.LNX.4.61.0504122156050.17411@netcore.fi>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com>
 <Pine.LNX.4.61.0504120957010.3431@netcore.fi> <20050412165344.GA6652@vaf-lnx1.cisco.com>
 <Pine.LNX.4.61.0504122040050.16404@netcore.fi> <20050412183725.GA8539@vaf-lnx1.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

On Tue, 12 Apr 2005, Vince Fuller wrote:
> Hmm. I am very wary of expanding the scope of this document; the hope is that,
> being simply an update and clarification of RFC1519, it will be fairly easy to
> get through the standards process. The food-fight over RFC1519 and CIDRD was
> pretty ugly; I don't think anybody wants to go through that again.

The key word here is, I believe, "was".  10 years of operational 
experience, 99.99% of deployment, etc. has hopefully made the food 
fights moot.. and now all that remains is cleaning up the results.

Just one simple spec should do just fine, I think.

> Do you really think that the new draft, as currently written, covers all of
> the ground of 1467, 1481, 1482, 1517, 1518, 1520, and 1817? I can well believe
> that many, if not most, of those documents should be re-classified as
> "historical" as part of the NEWTRK effort but that seems beyond the
> scope of the RFC1519-rewrite.

I've not done extensive review of the documents, but based on quick 
look at them, I doubt more than 1-2 pages of added text (at maximum) 
would be required to include the vital bits of the other, 
should-be-Historic documents.  Maybe about one paragraph each, 
describing why it is no longer relevant.

>   This memo discusses the strategy for address assignment of the
>   existing 32-bit IPv4 address space with a view toward conserving the
>   address space and limiting the growth rate of global routing state.
>   This document makes the original CIDR spec [RFC1519] obsolete, with
>   changes made both to clarify the concepts it introduced and, after
>   more than twelve years, to update the Internet community on the
>   results of deploying the technology described.
>
> How is that? While grammatically correct, using "obsolete" as a verb seems a
> little awkward to me...

Good enough. 'Obsoletes' as a verb is established terminology for 
RFC-editor guidance, so it should be OK.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Tue Apr 12 16:39:09 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08250
	for <grow-archive@lists.ietf.org>; Tue, 12 Apr 2005 16:39:09 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CKbMx1019615;
	Tue, 12 Apr 2005 13:37:22 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3CKbM7N019608;
	Tue, 12 Apr 2005 13:37:22 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3CKbLvF019412
	for <grow@lists.uoregon.edu>; Tue, 12 Apr 2005 13:37:22 -0700 (PDT)
Received: from sj-core-4.cisco.com (171.68.223.138)
  by sj-iport-4.cisco.com with ESMTP; 12 Apr 2005 13:37:16 -0700
Received: from cisco.com (vaf-lnx1.cisco.com [171.71.140.59])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j3CKbE05018224;
	Tue, 12 Apr 2005 13:37:14 -0700 (PDT)
Received: from vaf-lnx1.cisco.com (vaf-lnx1 [127.0.0.1])
	by cisco.com (8.12.11/8.12.11) with ESMTP id j3CKbDRc010773;
	Tue, 12 Apr 2005 13:37:13 -0700
Received: (from vaf@localhost)
	by vaf-lnx1.cisco.com (8.12.11/8.12.11/Submit) id j3CKbDZl010771;
	Tue, 12 Apr 2005 13:37:13 -0700
X-Authentication-Warning: vaf-lnx1.cisco.com: vaf set sender to vaf@cisco.com using -f
Date: Tue, 12 Apr 2005 13:37:13 -0700
From: Vince Fuller <vaf@cisco.com>
To: Pekka Savola <pekkas@netcore.fi>
Cc: grow@lists.uoregon.edu
Subject: Re: grow: draft of new RFC1519 replacement
Message-ID: <20050412203713.GA10692@vaf-lnx1.cisco.com>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504120957010.3431@netcore.fi> <20050412165344.GA6652@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504122040050.16404@netcore.fi> <20050412183725.GA8539@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504122156050.17411@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.61.0504122156050.17411@netcore.fi>
User-Agent: Mutt/1.4.1i
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

> The key word here is, I believe, "was".  10 years of operational 
> experience, 99.99% of deployment, etc. has hopefully made the food 
> fights moot.. and now all that remains is cleaning up the results.

Maybe. In the past 12 years, the IETF world has become ever more politicized
and vendor-oriented. Nowadays, it seems like it takes years to make even the
simplest of changes to a standards-track document. And given sensitivities
regarding the relevance (or lack thereof) of IPv6, a re-issued CIDR spec would
seem a nice target for controversy. After having lived through that once, I
think I can safely speak for Tony when I say that neither of us want to go
through it again.

> I've not done extensive review of the documents, but based on quick 
> look at them, I doubt more than 1-2 pages of added text (at maximum) 
> would be required to include the vital bits of the other, 
> should-be-Historic documents.  Maybe about one paragraph each, 
> describing why it is no longer relevant.

As I said many times to the early reviewers of this document, I welcome
suggested text :-)

	--Vince
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Wed Apr 13 18:13:50 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12657
	for <grow-archive@lists.ietf.org>; Wed, 13 Apr 2005 18:13:50 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3DM9XLj004366;
	Wed, 13 Apr 2005 15:09:33 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3DM9Xjg004365;
	Wed, 13 Apr 2005 15:09:33 -0700 (PDT)
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3DM9WnS004255
	for <grow@lists.uoregon.edu>; Wed, 13 Apr 2005 15:09:32 -0700 (PDT)
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 13 Apr 2005 15:09:18 -0700
X-IronPort-AV: i="3.92,98,1112598000"; 
   d="scan'208"; a="249310312:sNHT3501053780"
Received: from cisco.com (vaf-lnx1.cisco.com [171.71.140.59])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j3DM9BlG011455
	for <grow@lists.uoregon.edu>; Wed, 13 Apr 2005 15:09:12 -0700 (PDT)
Received: from vaf-lnx1.cisco.com (vaf-lnx1 [127.0.0.1])
	by cisco.com (8.12.11/8.12.11) with ESMTP id j3DM9FcR008310
	for <grow@lists.uoregon.edu>; Wed, 13 Apr 2005 15:09:15 -0700
Received: (from vaf@localhost)
	by vaf-lnx1.cisco.com (8.12.11/8.12.11/Submit) id j3DM9FSX008308
	for grow@lists.uoregon.edu; Wed, 13 Apr 2005 15:09:15 -0700
X-Authentication-Warning: vaf-lnx1.cisco.com: vaf set sender to vaf@cisco.com using -f
Date: Wed, 13 Apr 2005 15:09:15 -0700
From: Vince Fuller <vaf@cisco.com>
To: grow@lists.uoregon.edu
Subject: Re: grow: draft of new RFC1519 replacement
Message-ID: <20050413220915.GA8160@vaf-lnx1.cisco.com>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504120957010.3431@netcore.fi> <20050412165344.GA6652@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504122040050.16404@netcore.fi> <20050412183725.GA8539@vaf-lnx1.cisco.com> <20050412184322.GB29466@nexthop.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050412184322.GB29466@nexthop.com>
User-Agent: Mutt/1.4.1i
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

> If I might suggest:
> 
> On Tue, Apr 12, 2005 at 11:37:25AM -0700, Vince Fuller wrote:
> >    This document makes the original CIDR spec [RFC1519] obsolete,
> 
> This document obsoletes the ....

Since this has now been requested by multiple people, I have made the
requested change... still don't like "obsolete" as a verb, but I guess
it is in common use now.

Latest draft is at http://www.employees.org/~vaf/draft-vaf-cidrupdate-00.txt

It has been suggested that this become a GROW WG document. Any opinions on
whether that is a good or bad idea?

	--Vince
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Wed Apr 13 20:57:38 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24924
	for <grow-archive@lists.ietf.org>; Wed, 13 Apr 2005 20:57:38 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3E0t3Fo010956;
	Wed, 13 Apr 2005 17:55:03 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3E0t3RI010955;
	Wed, 13 Apr 2005 17:55:03 -0700 (PDT)
Received: from challah.msrl.com (challah.msrl.com [198.137.194.222])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3E0t1UY010866
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <grow@lists.uoregon.edu>; Wed, 13 Apr 2005 17:55:02 -0700 (PDT)
Received: (qmail 3664 invoked by uid 211); 14 Apr 2005 00:54:57 -0000
Received: from 20.sub-70-216-158.myvzw.com (HELO ?70.216.158.20?) (vgill@70.216.158.20)
  by challah.msrl.com with RC4-MD5 encrypted SMTP; 14 Apr 2005 00:54:57 -0000
Message-ID: <425DBF5D.8030501@vijaygill.com>
Date: Wed, 13 Apr 2005 20:54:53 -0400
From: vijay gill <vgill@vijaygill.com>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Vince Fuller <vaf@cisco.com>
CC: grow@lists.uoregon.edu
Subject: Re: grow: draft of new RFC1519 replacement
References: <20050411170200.GA11870@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504120957010.3431@netcore.fi> <20050412165344.GA6652@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504122040050.16404@netcore.fi> <20050412183725.GA8539@vaf-lnx1.cisco.com> <20050412184322.GB29466@nexthop.com> <20050413220915.GA8160@vaf-lnx1.cisco.com>
In-Reply-To: <20050413220915.GA8160@vaf-lnx1.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vince Fuller wrote:
>>If I might suggest:
>>
>>On Tue, Apr 12, 2005 at 11:37:25AM -0700, Vince Fuller wrote:
>>
>>>   This document makes the original CIDR spec [RFC1519] obsolete,
>>
>>This document obsoletes the ....
> 
> 
> Since this has now been requested by multiple people, I have made the
> requested change... still don't like "obsolete" as a verb, but I guess
> it is in common use now.
> 
> Latest draft is at http://www.employees.org/~vaf/draft-vaf-cidrupdate-00.txt
> 
> It has been suggested that this become a GROW WG document. Any opinions on
> whether that is a good or bad idea?

I like the orginal wording fwiw.  Also, this definitely makes sense for 
the GROW wg as a document, in that it deals with global routing 
operations and I think CIDR has had a fair bit of impact on global 
routing and operations, including filtering policies etc.

/vijay
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Wed Apr 13 21:35:37 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27387
	for <grow-archive@lists.ietf.org>; Wed, 13 Apr 2005 21:35:37 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3E1YKjP014821;
	Wed, 13 Apr 2005 18:34:20 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3E1YKLb014793;
	Wed, 13 Apr 2005 18:34:20 -0700 (PDT)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3E1YJ1E014679
	for <grow@lists.uoregon.edu>; Wed, 13 Apr 2005 18:34:19 -0700 (PDT)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.2/8.13.2) with ESMTP id j3E1XIG4022316;
	Wed, 13 Apr 2005 18:33:18 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.2/8.12.11/Submit) id j3E1XIii022315;
	Wed, 13 Apr 2005 18:33:18 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Wed, 13 Apr 2005 18:33:18 -0700
From: David Meyer <dmm@1-4-5.net>
To: vijay gill <vgill@vijaygill.com>
Cc: Vince Fuller <vaf@cisco.com>, grow@lists.uoregon.edu
Subject: Re: grow: draft of new RFC1519 replacement
Message-ID: <20050414013318.GA22296@1-4-5.net>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504120957010.3431@netcore.fi> <20050412165344.GA6652@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504122040050.16404@netcore.fi> <20050412183725.GA8539@vaf-lnx1.cisco.com> <20050412184322.GB29466@nexthop.com> <20050413220915.GA8160@vaf-lnx1.cisco.com> <425DBF5D.8030501@vijaygill.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="5mCyUwZo2JvN/JJP"
Content-Disposition: inline
In-Reply-To: <425DBF5D.8030501@vijaygill.com>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader, Star Wars Episode IV.
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk


--5mCyUwZo2JvN/JJP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 13, 2005 at 08:54:53PM -0400, vijay gill wrote:
> Vince Fuller wrote:
> >>If I might suggest:
> >>
> >>On Tue, Apr 12, 2005 at 11:37:25AM -0700, Vince Fuller wrote:
> >>
> >>>  This document makes the original CIDR spec [RFC1519] obsolete,
> >>
> >>This document obsoletes the ....
> >
> >
> >Since this has now been requested by multiple people, I have made the
> >requested change... still don't like "obsolete" as a verb, but I guess
> >it is in common use now.
> >
> >Latest draft is at=20
> >http://www.employees.org/~vaf/draft-vaf-cidrupdate-00.txt
> >
> >It has been suggested that this become a GROW WG document. Any opinions =
on
> >whether that is a good or bad idea?
>=20
> I like the orginal wording fwiw.  Also, this definitely makes sense for=
=20
> the GROW wg as a document, in that it deals with global routing=20
> operations and I think CIDR has had a fair bit of impact on global=20
> routing and operations, including filtering policies etc.

	Now that this is open, can folks let us know what you
	think about this document becoming a WG document.

	Thanks,

	Dave & Geoff

--5mCyUwZo2JvN/JJP
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCXcheORgD1qCZ2KcRAiC5AJ9Q2wnS/Z8azWr6yUSD0NsgsLPf3ACgk8X5
Ukq1FCszyPN7fKfVq6JhgLA=
=pVQR
-----END PGP SIGNATURE-----

--5mCyUwZo2JvN/JJP--
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Wed Apr 13 22:50:56 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02066
	for <grow-archive@lists.ietf.org>; Wed, 13 Apr 2005 22:50:56 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3E2n0Pr004509;
	Wed, 13 Apr 2005 19:49:00 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3E2n0qJ004505;
	Wed, 13 Apr 2005 19:49:00 -0700 (PDT)
Received: from felix.automagic.org (felix.hopcount.ca [204.152.186.101])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3E2mx4k004489
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <grow@lists.uoregon.edu>; Wed, 13 Apr 2005 19:48:59 -0700 (PDT)
Received: from [199.212.90.16] (helo=[199.212.90.16])
	by felix.automagic.org with esmtpsa (TLSv1:RC4-SHA:128)
	(Exim 4.42 (FreeBSD))
	id 1DLuPX-0009LM-G3; Thu, 14 Apr 2005 02:48:55 +0000
In-Reply-To: <20050414013318.GA22296@1-4-5.net>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504120957010.3431@netcore.fi> <20050412165344.GA6652@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504122040050.16404@netcore.fi> <20050412183725.GA8539@vaf-lnx1.cisco.com> <20050412184322.GB29466@nexthop.com> <20050413220915.GA8160@vaf-lnx1.cisco.com> <425DBF5D.8030501@vijaygill.com> <20050414013318.GA22296@1-4-5.net>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <77e29030a2d9a5331a799a4be2cc4ef3@isc.org>
Content-Transfer-Encoding: 7bit
Cc: vijay gill <vgill@vijaygill.com>, Vince Fuller <vaf@cisco.com>,
        grow@lists.uoregon.edu
From: Joe Abley <jabley@isc.org>
Subject: Re: grow: draft of new RFC1519 replacement
Date: Wed, 13 Apr 2005 22:48:23 -0400
To: David Meyer <dmm@1-4-5.net>
X-Mailer: Apple Mail (2.619.2)
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit


On 13 Apr 2005, at 21:33, David Meyer wrote:

> 	Now that this is open, can folks let us know what you
> 	think about this document becoming a WG document.

I can't think of a better place for it. Makes sense to me.


Joe

_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Wed Apr 13 22:56:09 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA02709
	for <grow-archive@lists.ietf.org>; Wed, 13 Apr 2005 22:56:09 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3E2o99H005391;
	Wed, 13 Apr 2005 19:50:09 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3E2o9Fg005386;
	Wed, 13 Apr 2005 19:50:09 -0700 (PDT)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3E2o8W5005366
	for <grow@lists.uoregon.edu>; Wed, 13 Apr 2005 19:50:08 -0700 (PDT)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.2/8.13.2) with ESMTP id j3E2o7ts024126;
	Wed, 13 Apr 2005 19:50:07 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.2/8.12.11/Submit) id j3E2o7DF024125;
	Wed, 13 Apr 2005 19:50:07 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Wed, 13 Apr 2005 19:50:07 -0700
From: David Meyer <dmm@1-4-5.net>
To: Joe Abley <jabley@isc.org>
Cc: vijay gill <vgill@vijaygill.com>, Vince Fuller <vaf@cisco.com>,
        grow@lists.uoregon.edu
Subject: Re: grow: draft of new RFC1519 replacement
Message-ID: <20050414025007.GA24110@1-4-5.net>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504120957010.3431@netcore.fi> <20050412165344.GA6652@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504122040050.16404@netcore.fi> <20050412183725.GA8539@vaf-lnx1.cisco.com> <20050412184322.GB29466@nexthop.com> <20050413220915.GA8160@vaf-lnx1.cisco.com> <425DBF5D.8030501@vijaygill.com> <20050414013318.GA22296@1-4-5.net> <77e29030a2d9a5331a799a4be2cc4ef3@isc.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo"
Content-Disposition: inline
In-Reply-To: <77e29030a2d9a5331a799a4be2cc4ef3@isc.org>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader, Star Wars Episode IV.
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk


--envbJBWh7q8WU6mo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 13, 2005 at 10:48:23PM -0400, Joe Abley wrote:
>=20
> On 13 Apr 2005, at 21:33, David Meyer wrote:
>=20
> >	Now that this is open, can folks let us know what you
> >	think about this document becoming a WG document.
>=20
> I can't think of a better place for it. Makes sense to me.

	Noted.

	Thanks Joe.

	Dave

--envbJBWh7q8WU6mo
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCXdpfORgD1qCZ2KcRAjj5AJ9teCfudbGo53o6YNMA2fSYhJG/MgCdEHSx
dye80FPBp5cA5Jm+Ce0KN/Y=
=dR3N
-----END PGP SIGNATURE-----

--envbJBWh7q8WU6mo--
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Wed Apr 13 23:40:58 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05327
	for <grow-archive@lists.ietf.org>; Wed, 13 Apr 2005 23:40:58 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3E3dIAu004607;
	Wed, 13 Apr 2005 20:39:19 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3E3dIvS004606;
	Wed, 13 Apr 2005 20:39:18 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3E3dHFL004586
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <grow@lists.uoregon.edu>; Wed, 13 Apr 2005 20:39:18 -0700 (PDT)
Received: from [205.168.100.50] (dhcp1.tcb.net [205.168.100.50])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by dog.tcb.net (Postfix) with ESMTP id 33783645CA
	for <grow@lists.uoregon.edu>; Wed, 13 Apr 2005 21:39:58 -0600 (MDT)
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <425DBF5D.8030501@vijaygill.com>
References: <20050411170200.GA11870@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504120957010.3431@netcore.fi> <20050412165344.GA6652@vaf-lnx1.cisco.com> <Pine.LNX.4.61.0504122040050.16404@netcore.fi> <20050412183725.GA8539@vaf-lnx1.cisco.com> <20050412184322.GB29466@nexthop.com> <20050413220915.GA8160@vaf-lnx1.cisco.com> <425DBF5D.8030501@vijaygill.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <8469ee40757270a54de93be37954cad9@tcb.net>
Content-Transfer-Encoding: 7bit
From: Danny McPherson <danny@tcb.net>
Subject: Re: grow: draft of new RFC1519 replacement
Date: Wed, 13 Apr 2005 21:39:13 -0600
To: grow@lists.uoregon.edu
X-Mailer: Apple Mail (2.619.2)
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk
Content-Transfer-Encoding: 7bit


On Apr 13, 2005, at 6:54 PM, vijay gill wrote:

> I like the orginal wording fwiw.  Also, this definitely makes sense 
> for the GROW wg as a document, in that it deals with global routing 
> operations and I think CIDR has had a fair bit of impact on global 
> routing and operations, including filtering policies etc.

I agree with Vijay on both points...

-danny

_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From steinbeck@yebox.com  Thu Apr 14 04:56:39 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16480;
	Thu, 14 Apr 2005 04:56:38 -0400 (EDT)
Received: from [218.156.117.100] (helo=132.151.6.1)
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1DM0JM-0005gE-VS; Thu, 14 Apr 2005 05:06:58 -0400
Received: from coup-jcoppens.com (EHLO ziegler.jcoppens.com) 
  by egret.jcoppens.com with SMTP; Thu, 14 Apr 2005 10:52:45 +0100
Date: Thu, 14 Apr 2005 14:54:45 +0500
From: "Casandra Salas" <steinbeck@yebox.com>
To: gcunning@ietf.org
Cc: gency@ietf.org, geopriv@ietf.org, geopriv-admin@ietf.org,
        geopriv-web-archive@ietf.org, gga8k2ijd9ai7232@ietf.org,
        ghostsender-a.3feet.com@ietf.org, grow-archive@ietf.org, gsmp@ietf.org,
        gsmp-admin@ietf.org, gsmp-archive@ietf.org, gsmp-web-archive@ietf.org,
        haley.bledsoe@ietf.org, hive@ietf.org, hsc@ietf.org
Subject: Rates fixed 
Message-ID: <BKELLDAGKABIOCHDFD165DGAA.danny326@virgilio.it>
X-SpamTest-Info: Profile: SysLog
X-SpamTest-Status: Not detected
X-SpamTest-Version: SMTP-Filter Version 2.0.0 [073], SpamtestISP/Release
X-Mailer: MIME-tools 5.41 (Entity 5.404)
X-Spam-Score: 5.6 (+++++)
X-Spam-Flag: YES
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.mrg-now-yes.com/sign.asp



 Best Regards,

 Fidel Field
 
 to be remov(ed:	http://www.mrg-now-yes.com/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From owner-grow@lists.uoregon.edu  Thu Apr 14 15:49:08 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16817
	for <grow-archive@lists.ietf.org>; Thu, 14 Apr 2005 15:49:07 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3EJhLRi027716;
	Thu, 14 Apr 2005 12:43:21 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3EJhLjr027705;
	Thu, 14 Apr 2005 12:43:21 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3EJhJ0L027637
	for <grow@lists.uoregon.edu>; Thu, 14 Apr 2005 12:43:20 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16213;
	Thu, 14 Apr 2005 15:43:15 -0400 (EDT)
Message-Id: <200504141943.PAA16213@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: grow@lists.uoregon.edu
From: Internet-Drafts@ietf.org
Subject: grow: I-D ACTION:draft-ietf-grow-bgp-wedgies-02.txt
Date: Thu, 14 Apr 2005 15:43:15 -0400
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Global Routing Operations Working Group of the IETF.

	Title		: BGP Wedgies
	Author(s)	: T. Griffin, G. Huston
	Filename	: draft-ietf-grow-bgp-wedgies-02.txt
	Pages		: 10
	Date		: 2005-4-14
	
It has commonly been assumed that the Border Gateway Protocol (BGP)
   is a tool for distributing reachability information in a manner that
   creates forwarding paths in a deterministic manner.  In this memo we
   will describe a class of BGP configurations for which there is more
   than one potential outcome, and where forwarding states other than
   the intended state are equally stable, and that the stable state
   where BGP converges may be selected by BGP in a non-deterministic
   manner.  These stable, but unintended, BGP states are termed here
   "BGP Wedgies".

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-bgp-wedgies-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-grow-bgp-wedgies-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-grow-bgp-wedgies-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2005-4-14161749.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-grow-bgp-wedgies-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-grow-bgp-wedgies-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2005-4-14161749.I-D@ietf.org>

--OtherAccess--

--NextPart--


_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From unyokes@mailAccount.com  Thu Apr 14 16:21:13 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20892;
	Thu, 14 Apr 2005 16:21:13 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMAzx-0000Bc-NZ; Thu, 14 Apr 2005 16:31:38 -0400
Received: from m37.net81-65-236.noos.fr ([81.65.236.37])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1DMApn-0002XG-CS; Thu, 14 Apr 2005 16:21:11 -0400
Delivered-To: amoco@nakayama.dreamhost.com
Received: from ascertain.dreamhost.com by nonetheless.dreamhost.com (Pingofix) with ESMTP id 8CC1A72D3B
        for <lista-gcunning@ietf.org>;
        Fri, 15 Apr 2005 02:09:52 +0500
Message-ID: <BKELLDAGKABIOCHDFD596DGAA.danngcunning@ietf.org>
Date: Thu, 14 Apr 2005 19:10:52 -0200
From: "Francesca Shapiro" <unyokes@mailAccount.com>
To: <gcunning@ietf.org>
Subject: Your account #84M7672
X-Mailer: Mailman v2.0.2
X-SpamTest-Info: Profile: Formal (167/041167)
X-SpamTest-Info: Profile: Detect Hard No RBL (4/030587)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.mrg-now-yes.com/sign.asp



 Best Regards,

 Kelsey Pickens
 
 to be remov(ed:	http://www.mrg-now-yes.com/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From lentigo@mailAccount.com  Thu Apr 14 16:49:07 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25706;
	Thu, 14 Apr 2005 16:49:07 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMBQw-0001xw-KZ; Thu, 14 Apr 2005 16:59:34 -0400
Received: from [210.205.129.150] (helo=65.246.255.50)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1DMBGq-0003LD-FV; Thu, 14 Apr 2005 16:49:05 -0400
Delivered-To: pigeonfoot@ibn.dreamhost.com
Received: from loquacious.dreamhost.com by deify.dreamhost.com (Pingofix) with ESMTP id 9CC0A90D9B
        for <lista-gcunning@ietf.org>;
        Fri, 15 Apr 2005 02:39:39 +0500
Message-ID: <BKELLDAGKABIOCHDFD064DGAA.danngcunning@ietf.org>
Date: Thu, 14 Apr 2005 20:45:39 -0100
From: "Ethel Adair" <lentigo@mailAccount.com>
To: <gcunning@ietf.org>
Subject: Your account #206M7674
X-Mailer: Mailman v2.0.1
X-SpamTest-Info: Profile: Formal (167/041144)
X-SpamTest-Info: Profile: Detect Hard No RBL (4/030562)
X-Spam-Score: 7.9 (+++++++)
X-Spam-Flag: YES
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.mrg-now-yes.com/sign.asp



 Best Regards,

 Mohammad Connolly
 
 to be remov(ed:	http://www.mrg-now-yes.com/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From leut@mailAccount.com  Fri Apr 15 06:50:10 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16221;
	Fri, 15 Apr 2005 06:50:10 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMOZ1-0008Tm-5a; Fri, 15 Apr 2005 07:00:44 -0400
Received: from [220.82.13.200] (helo=65.246.255.50)
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1DMNfQ-0004RP-7I; Fri, 15 Apr 2005 06:03:17 -0400
Received: from tambourine-jcoppens.com (EHLO ponchartrain.jcoppens.com) 
  by hopeful.jcoppens.com with SMTP; Fri, 15 Apr 2005 14:40:59 +0300
Date: Fri, 15 Apr 2005 16:42:59 +0500
From: "Daphne Mora" <leut@mailAccount.com>
To: gcunning@ietf.org
Cc: gency@ietf.org, geopriv@ietf.org, geopriv-admin@ietf.org,
        geopriv-web-archive@ietf.org, gga8k2ijd9ai7232@ietf.org,
        ghostsender-a.3feet.com@ietf.org, grow-archive@ietf.org
Subject: Become one of the low rates
Message-ID: <BKELLDAGKABIOCHDFD549DGAA.danny586@virgilio.it>
X-SpamTest-Info: Profile: SysLog
X-SpamTest-Status: Not detected
X-SpamTest-Version: SMTP-Filter Version 2.0.0 [572], SpamtestISP/Release
X-Mailer: MIME-tools 5.41 (Entity 5.404)
X-Spam-Score: 5.6 (+++++)
X-Spam-Flag: YES
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.n0wwewillsave.com/sign.asp



 Best Regards,

 Wesley Fulton
 
 to be remov(ed:	http://www.n0wwewillsave.com/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


From owner-grow@lists.uoregon.edu  Fri Apr 15 12:21:30 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18474
	for <grow-archive@lists.ietf.org>; Fri, 15 Apr 2005 12:21:30 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3FGIZHB008173;
	Fri, 15 Apr 2005 09:18:36 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3FGIZh8008169;
	Fri, 15 Apr 2005 09:18:35 -0700 (PDT)
Received: from m106.maoz.com (m106.maoz.com [205.167.76.9])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3FGIZP7008141
	for <grow@lists.uoregon.edu>; Fri, 15 Apr 2005 09:18:35 -0700 (PDT)
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.13.2/8.13.2) with ESMTP id j3FGINTp028366;
	Fri, 15 Apr 2005 09:18:23 -0700
Received: (from dmm@localhost)
	by m106.maoz.com (8.13.2/8.12.11/Submit) id j3FGIJc5028365;
	Fri, 15 Apr 2005 09:18:19 -0700
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Fri, 15 Apr 2005 09:18:19 -0700
From: David Meyer <dmm@1-4-5.net>
To: grow@lists.uoregon.edu
Cc: gih@apnic.net
Subject: grow: WGLC #2 on draft-ietf-grow-bgp-wedgies-02.txt
Message-ID: <20050415161819.GA28335@1-4-5.net>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO"
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-gpg-fingerprint: 2409 8B50 B389 A307 BA5C 2A16 3918 03D6 A099 D8A7
X-philosophy: "I find your lack of faith disturbing." -- Darth Vader, Star Wars Episode IV.
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk


--2oS5YaxWCcQjTEyO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable


	Folks

	This note starts a second WG Last Call for comments
	on draft-ietf-grow-bgp-wedgies-02.txt, "BGP Wedgies".
	It can be found on=20
=09
	ftp://ftp.ietf.org/internet-drafts/draft-ietf-grow-bgp-wedgies-02.txt

	Please review the document carefully, and send your
	feedback to the list.  Please also indicate whether or
	not you believe that this document is ready to go to the
	IESG.=20

	This Last Call will end on 29 Apr 2005 at 1400 PDT (UTC/GMT-7).

	Thanks,

	Dave













On Thu, Apr 14, 2005 at 03:43:15PM -0400, Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Global Routing Operations Working Group =
of the IETF.
>=20
> 	Title		: BGP Wedgies
> 	Author(s)	: T. Griffin, G. Huston
> 	Filename	: draft-ietf-grow-bgp-wedgies-02.txt
> 	Pages		: 10
> 	Date		: 2005-4-14
> =09
> It has commonly been assumed that the Border Gateway Protocol (BGP)
>    is a tool for distributing reachability information in a manner that
>    creates forwarding paths in a deterministic manner.  In this memo we
>    will describe a class of BGP configurations for which there is more
>    than one potential outcome, and where forwarding states other than
>    the intended state are equally stable, and that the stable state
>    where BGP converges may be selected by BGP in a non-deterministic
>    manner.  These stable, but unintended, BGP states are termed here
>    "BGP Wedgies".
>=20
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-grow-bgp-wedgies-02.txt
>=20
> To remove yourself from the I-D Announcement list, send a message to=20
> i-d-announce-request@ietf.org with the word unsubscribe in the body of th=
e message. =20
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20
> to change your subscription settings.
>=20
>=20
> Internet-Drafts are also available by anonymous FTP. Login with the usern=
ame
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-grow-bgp-wedgies-02.txt".
>=20
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html=20
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
>=20
> Internet-Drafts can also be obtained by e-mail.
>=20
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-grow-bgp-wedgies-02.txt".
> =09
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 	=09
> 	=09
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.



--2oS5YaxWCcQjTEyO
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCX+lLORgD1qCZ2KcRAmRJAJ4uP8vqofinulcyHJ3Gzh+UNHMJJACcCKTw
lGgjWd/Ic5tefMg6rdm1Lng=
=YyR+
-----END PGP SIGNATURE-----

--2oS5YaxWCcQjTEyO--
_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From owner-grow@lists.uoregon.edu  Fri Apr 15 15:36:30 2005
Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09018
	for <grow-archive@lists.ietf.org>; Fri, 15 Apr 2005 15:36:29 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3FJYBBP015657;
	Fri, 15 Apr 2005 12:34:11 -0700 (PDT)
Received: (from majordom@localhost)
	by darkwing.uoregon.edu (8.13.4/8.13.4/Submit) id j3FJYB7W015648;
	Fri, 15 Apr 2005 12:34:11 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by darkwing.uoregon.edu (8.13.4/8.13.4) with ESMTP id j3FJY9wl015526
	for <grow@lists.uoregon.edu>; Fri, 15 Apr 2005 12:34:10 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08262;
	Fri, 15 Apr 2005 15:34:07 -0400 (EDT)
Message-Id: <200504151934.PAA08262@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
Cc: grow@lists.uoregon.edu
From: Internet-Drafts@ietf.org
Subject: grow: I-D ACTION:draft-ietf-grow-rfc1519bis-00.txt
Date: Fri, 15 Apr 2005 15:34:07 -0400
Sender: owner-grow@lists.uoregon.edu
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Global Routing Operations Working Group of the IETF.

	Title		: Classless Inter-Domain Routing (CIDR): 
			  The Internet Address Assignment and Aggregation Plan
	Author(s)	: V. Fuller, T. Li
	Filename	: draft-ietf-grow-rfc1519bis-00.txt
	Pages		: 26
	Date		: 2005-4-15
	
This memo discusses the strategy for address assignment of the
   existing 32-bit IPv4 address space with a view toward conserving the
   address space and limiting the growth rate of global routing state.
   This document obsoletes the original CIDR spec [RFC1519], with
   changes made both to clarify the concepts it introduced and, after
   more than twelve years, to update the Internet community on the
   results of deploying the technology described.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-grow-rfc1519bis-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-grow-rfc1519bis-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-grow-rfc1519bis-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2005-4-15152505.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-grow-rfc1519bis-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-grow-rfc1519bis-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2005-4-15152505.I-D@ietf.org>

--OtherAccess--

--NextPart--


_________________________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/grow.html
web archive:        http://darkwing.uoregon.edu/~llynch/grow/


From appa@didamail.com  Fri Apr 15 17:40:10 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29174;
	Fri, 15 Apr 2005 17:40:03 -0400 (EDT)
Received: from host50.foretec.com ([65.246.255.50] helo=mx2.foretec.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMYi2-0003C1-60; Fri, 15 Apr 2005 17:50:43 -0400
Received: from 5354e96b.cable.casema.nl ([83.84.233.107])
	by mx2.foretec.com with smtp (Exim 4.24)
	id 1DMYXZ-0006G1-P8; Fri, 15 Apr 2005 17:39:54 -0400
Received: from lauderdale-jcoppens.com (EHLO swing.jcoppens.com) 
  by beforehand.jcoppens.com with SMTP; Fri, 15 Apr 2005 23:38:01 +0100
Date: Fri, 15 Apr 2005 16:30:01 -0600
From: "Joanna Kerr" <appa@didamail.com>
To: g-admin@ietf.org
Cc: g-web-archive@ietf.org, gchairs@ietf.org, gcunning@ietf.org,
        gency@ietf.org, geopriv@ietf.org, geopriv-admin@ietf.org,
        geopriv-web-archive@ietf.org, gga8k2ijd9ai7232@ietf.org,
        ghostsender-a.3feet.com@ietf.org, grow-archive@ietf.org, gsmp@ietf.org
Subject: Become one of the low rates
Message-ID: <BKELLDAGKABIOCHDFD527DGAA.danny616@virgilio.it>
X-SpamTest-Info: Profile: SysLog
X-SpamTest-Status: Not detected
X-SpamTest-Version: SMTP-Filter Version 2.0.0 [712], SpamtestISP/Release
X-Mailer: MIME-tools 5.41 (Entity 5.404)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3

Hello,

 We tried contacting you awhile ago about your low interest morta(ge rate.

 You have qualified for the lowest rate in years...

 You could get over $380,000 for as little as $500 a month!

 Ba(d credit? Doesn't matter, low rates are fixed no matter what!

 
 To get a free, no obli,gation consultation click below:

 http://www.n0wwewillsave.com/sign.asp



 Best Regards,

 Elias Boone
 
 to be remov(ed:	http://www.n0wwewillsave.com/gone.asp

 this process takes one week, so please be patient. we do our 
 best to take your email/s off but you have to fill out a rem/ove
 or else you will continue to recieve email/s.


