[33551] in North American Network Operators' Group
from ppml@arin.net: SWIP policy resolution
daemon@ATHENA.MIT.EDU (Bennett Todd)
Tue Jan 16 09:39:42 2001
Date: Tue, 16 Jan 2001 09:37:04 -0500
From: Bennett Todd <bet@rahul.net>
To: nanog@merit.edu
Cc: Richard Jimmerson <richardj@arin.net>
Message-ID: <20010116093704.X28001@rahul.net>
Mail-Followup-To: ppml@arin.net
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
protocol="application/pgp-signature"; boundary="7kW37LRKoI6fR2de"
Content-Disposition: inline
In-Reply-To: <20010104122718.B25564@rahul.net>; from bet@rahul.net on Thu, Jan 04, 2001 at 12:27:18 -0500
Errors-To: owner-nanog-outgoing@merit.edu
--7kW37LRKoI6fR2de
Content-Type: multipart/mixed; boundary="Ln+iIw7POnzHEEo5"
Content-Disposition: inline
--Ln+iIw7POnzHEEo5
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
I earlier forwarded the question from ARIN soliciting feedback on a
question; they just announced the resolution of the question on the
ppml list, and I got permission to forward their note to this forum.
As before, if you disapprove of the cross-list forwarding please
complain to me directly as this is solely my fault, and if you wish
to discuss the topic of the posting I've tried to set the
Mail-Followup-To header to direct discussions to the ppml list.
-Bennett
--Ln+iIw7POnzHEEo5
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <owner-ppml@arin.net>
Delivered-To: bet@og.latency.net
Received: from betlap [127.0.0.1]
by localhost with IMAP (fetchmail-5.6.2)
for bet@localhost (single-drop); Tue, 16 Jan 2001 09:08:52 -0500 (EST)
Received: from latency.net (pimpbox.latency.net [209.123.200.18])
by og.latency.net (Postfix) with SMTP id 29DDA13FB27
for <bet@og.latency.net>; Tue, 16 Jan 2001 09:09:20 -0500 (EST)
Received: (qmail 4923 invoked by uid 593); 16 Jan 2001 14:08:19 -0000
Delivered-To: bet@latency.net
Received: (qmail 4910 invoked from network); 16 Jan 2001 14:08:19 -0000
Received: from yellow.rahul.net (postfix@192.160.13.18)
by pimpbox.latency.net with SMTP; 16 Jan 2001 14:08:19 -0000
Received: by yellow.rahul.net (Postfix)
id D15DA7CB0; Tue, 16 Jan 2001 06:08:25 -0800 (PST)
Delivered-To: bet@rahul.net
Received: from rs2.arin.net (rs2.arin.net [192.149.252.22])
by yellow.rahul.net (Postfix) with ESMTP id 2E97D7C93
for <bet@rahul.net>; Tue, 16 Jan 2001 06:08:25 -0800 (PST)
Received: from ops.arin.net (ops.arin.net [192.149.252.141])
by rs2.arin.net (8.9.3/8.9.3) with ESMTP id JAA25300;
Tue, 16 Jan 2001 09:04:41 -0500 (EST)
Received: (from majordom@localhost)
by ops.arin.net (8.9.0/8.9.0) id JAA01220
for ppml-outgoing; Tue, 16 Jan 2001 09:00:28 -0500 (EST)
Received: from snoopy ([192.149.252.226])
by ops.arin.net (8.9.0/8.9.0) with SMTP id JAA01216
for <ppml@arin.net>; Tue, 16 Jan 2001 09:00:27 -0500 (EST)
Reply-To: <richardj@arin.net>
From: "Richard Jimmerson" <richardj@arin.net>
To: <ppml@arin.net>
Subject: RE: Just to clarify
Date: Tue, 16 Jan 2001 09:00:26 -0500
Message-ID: <006201c07fc4$adfc8920$e2fc95c0@arin.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <Pine.LNX.4.21.0101051545020.15175-100000@varese.appliedtheory.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-ppml@arin.net
Precedence: bulk
ARIN has reviewed the discussions that have taken place
on this mailing list in regard to the practice of adding
maintainer IDs to reassigned records. We would like to
thank everyone who participated in this discussion.
Going forward, the practice of the ARIN registration staff
will be the following:
(Note we are using the well written summary provided by David Huberman)
If a provider who has been assigned address space from their upstream
wishes to assign address space further downstream, they are encouraged to
petition their upstream provider to re-SWIP the address space as an
allocation. If the upstream provider is unresponsive, the downstream
provider may then petition ARIN to enact this change. ARIN will make its
best attempt to contact the upstream provider to obtain their permission.
If the provider declines permission, ARIN will notify the petitioner as
such. If the provider is unresponsive after 10 business days, ARIN will
accede to the petitioner's request and notify the upstream of the
change(s).
Richard Jimmerson
Director of Operations
American Registry for Internet Numbers (ARIN)
--Ln+iIw7POnzHEEo5--
--7kW37LRKoI6fR2de
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE6ZFyQHZWg9mCTffwRAsqQAJ9Mww/82lfgJclc+O3mVpWHVWBJXwCfZqJp
5mf1XieAZGSM4Crh1z7Ppv4=
=dNg4
-----END PGP SIGNATURE-----
--7kW37LRKoI6fR2de--
