December 2006 - address-policy-wg

2006-07 Discussion Period extended until 17 January 2007 (First Raise in IPv4 Assignment Window Size)
by Filiz Yilmaz 04 Jan '07

04 Jan '07

PDP Number: 2006-07 First Raise in IPv4 Assignment Window Size Dear Colleagues The text of the policy proposal 2006-07 has changed. We have published the new version today, as a result the discussion period for this proposal will end on 17 January 2007. You can find the full proposal at: http://www.ripe.net/ripe/policies/proposals/2006-07.html We encourage you to review this policy proposal and send your comments to <address-policy-wg(a)ripe.net>. Regards Filiz Yilmaz RIPE NCC Policy Development Officer

14 22

32-bit AS Number Requests
by Dominic Spratley - Registration Services Manager 28 Dec '06

28 Dec '06

[Apologies for duplicate e-mails] Dear Colleagues, We are pleased to announce that from 1 January 2007 we will accept requests for 4-byte (32-bit) AS Numbers. The request form and supporting notes are available in the RIPE Document Store at: http://www.ripe.net/ripe/docs/asnrequestform.html http://www.ripe.net/ripe/docs/asnsupport.html Assignments will come from the following range: 3.0 - 3.1023 ASN32 objects will appear in the RIPE Database from 1 January 2007. Their format is different from the current 16-bit ASNs. The new format is described in these documents: http://www.ietf.org/internet-drafts/draft-michaelson-4byte-as-representatio… http://www.ietf.org/internet-drafts/draft-uijterwaal-rpsl-4byteas-ext-01.txt The introduction of 32-bit AS Numbers may have an effect on tools that query the RIPE Database or those based on RPSL. Kind Regards, Dominic Spratley Registration Services Manager RIPE NCC

1 0

Re: [address-policy-wg] 2006-07 Discussion Period extended until 17 January 2007 (First Raise in IPv4 Assignment Window Size)
by Erics 15 Dec '06

15 Dec '06

Hi, incentive and AW is a very bad combination. The AW should reflex the LIRs address requirement, and it must not be an incentive ! Hi Ingrid ;-) All in all I support the proposal to raise the AW automatically from 0 to /21 within six month. kind regards Eric Schmidt Deutsche Telekom AG T-Com Headquarters Network Information Center

1 0

Map of the Internet
by Shane Kerr 13 Dec '06

13 Dec '06

All, You've probably already seen it, but I thought it was cool enough to spam the list: http://xkcd.com/c195.html -- Shane

2 1

Re: [address-policy-wg] Allocation vs assignment question
by Makc The Great 04 Dec '06

04 Dec '06

So, overall consensus here is like this: On 12/4/06, Amar <amar(a)telia.net> wrote: > > Ergo: There has not to be any connection between > subnets for each assignment. It is done > based on the proven need and not on a > physical connection between the requesters > networks. > Could you please explain then what does "Sub-allocations are intended to aid the goal of routing aggregation" phrase means in english?

2 2

Allocation vs assignment question
by Makc The Great 04 Dec '06

04 Dec '06

Hello all, I have posted similar question at https://www.ripe.net/ripe/maillists/archives/db-help/2006/msg00040.html but I think that was not appropriate list, and I'm still not sure which is. My question is am I correct in assuming that all "assigned" IPs are on same physical network that all other IPs in their "sub-allocation" range? For example, here inetnum: 217.77.240.0 - 217.77.255.255 org: ORG-SW1-RIPE netname: DE-SAP-20001221 descr: SAP-AG Walldorf descr: ENTERPRISE country: DE status: ALLOCATED PA inetnum: 217.77.254.28 - 217.77.254.28 netname: SAP-JCrewGroupInc-US-i8 descr: J. Crew Group Inc. descr: US 770 Broadway, 14th Floor descr: Remote connection to SAP country: US status: ASSIGNED PA inetnum: 217.77.254.30 - 217.77.254.30 netname: SAP-AlumaFormDixieElectrical-US-i8 descr: Aluma-Form/Dixie Electrical descr: US 3625 Old Getwell Road descr: Remote connection to SAP country: US status: ASSIGNED PA are 217.77.254.28 and 217.77.254.30 still on german network, or are they physically located in US and connected to germany over some sort of intercontinental cable? Thanks, Max.

3 4