Send ARIN-PPML mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.arin.net/mailman/listinfo/arin-ppml
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of ARIN-PPML digest..."


Today's Topics:

   1. Re: ARIN-prop-186 Section 8.2 Reorganizations - Notice of
      intent to make editorial update (Chris Grundemann)
   2. Re: Draft Policy ARIN-2013-4: RIR Principles (Andrew Dul)
   3. Re: Draft Policy ARIN-2013-4: RIR Principles (William Herrin)
   4. Re: Draft Policy ARIN-2013-4: RIR Principles (William Herrin)
   5. Re: Draft Policy ARIN-2013-4: RIR Principles (Jason Schiller)


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

Message: 1
Date: Tue, 28 May 2013 10:34:57 -0600
From: Chris Grundemann <[email protected]>
To: ARIN <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [arin-ppml] ARIN-prop-186 Section 8.2 Reorganizations -
        Notice of intent to make editorial update
Message-ID:
        <cac1-dtkswxktgelu83v__alx3iwndtzck7rv39xt1y1two0...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Tue, May 28, 2013 at 9:54 AM, ARIN <[email protected]> wrote:
> The review period for this suggested administrative update to the NRPM ends
> tomorrow.

As such, now is the time to speak up if you have any concerns
regarding this change at all.

Thanks!
~Chris


>> The review period will close on 29 May 2013.
>
>
> Regards,
>
> Communications and Member Services
> American Registry for Internet Numbers (ARIN)
>
>
>
>
>
> On 4/29/13 2:24 PM, ARIN wrote:
>>
>> The ARIN Advisory Council (AC) met on 24 April 2013 and requested that
>> the following proposed editorial update to the Number Resource Policy
>> Manual (NRPM) be posted for review by the community.
>>
>> The AC provided the following statement:
>>
>> ----
>> "Having reviewed ARIN-prop-186 'Section 8.2 Reorganizations' the AC
>> believes that the requested change is editorial in nature. This
>> decision is based on the facts that the author of the current text did
>> not intend to remove reorganizations, that ARIN's operational
>> procedure will not change based on this update, as they currently
>> consider reorganizations to be valid. It was pointed out by staff that
>> unless the term were reintroduced into policy, their operational
>> procedure may have to change accordingly. Based on this position, the
>> ARIN AC proposes that the following editorial change be made to the
>> NRPM:
>>
>> Re-insert the word 'reorganization' into section 8.2; the resulting
>> text will read:
>>
>> "ARIN will consider requests for the transfer of number resources in
>> the case of mergers, acquisitions, and reorganizations under the
>> following conditions: ..."
>>
>> Please voice any concerns to the AC as soon as possible."
>> ----
>>
>> The process for editorial updates to the NRPM is found in Part One,
>> Section 3.1, paragraph 3 of the PDP:
>> "Changes to policy that are purely editorial and non-substantial in
>> nature are outside the scope of the full Policy Development Process and
>> may only be made with 30 days public notice followed by the concurrence
>> of both the ARIN Advisory Council and ARIN Board of Trustees that the
>> changes are non-substantial in nature."
>>
>> The review period will close on 29 May 2013.
>>
>> ARIN-prop-186 is below and available at:
>> https://www.arin.net/policy/proposals/
>>
>> The ARIN Policy Development Process is available at:
>> https://www.arin.net/policy/pdp.html
>>
>> Regards,
>>
>> Communications and Member Services
>> American Registry for Internet Numbers (ARIN)
>>
>>
>> ## * ##
>>
>>
>> Policy Proposal Name: Section 8.2 Reorganizations
>> Proposal Originator: John Springer
>>
>> Date: 23 April 2013
>>
>> Problem Statement:
>>
>> There is no longer a reference to corporate reorganizations in the
>> policy. ARIN often sees corporate reorganizations as the basis for
>> transfer.
>>
>> Corporate reorganizations were part of the previous version of 8.2
>> policy as follows:
>>
>> "ARIN will consider requests for the transfer of number resources only
>> upon receipt of evidence that the new entity has acquired the assets
>> which had, as of the date of the acquisition or proposed reorganization,
>> justified the current entity's use of the number resource."
>>
>> Current policy reads: "ARIN will consider requests for the transfer of
>> number resources in the case of mergers and acquisitions under the
>> following conditions: ..."
>>
>> Corporate reorganizations are currently being allowed under the
>> following conditions: A parent organization can transfer resources to a
>> child organization or vice versa as long as the child is a 100% wholly
>> owned subsidiary. Various documentary requirements apply.
>>
>> Policy statement:
>>
>> "ARIN will consider requests for the transfer of number resources in the
>> case of mergers, acquisitions and corporate reorganizations under the
>> following conditions: ..."
>>
>> Timetable for implementation: Immediately
>>
>>
>
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.



--
@ChrisGrundemann
http://chrisgrundemann.com


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

Message: 2
Date: Tue, 28 May 2013 11:19:50 -0700
From: Andrew Dul <[email protected]>
To: [email protected]
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-4: RIR Principles
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1

I support adding these guiding principles to the NRPM, furthermore I
would support efforts to introduce this policy in all RIR regions to
make this a global policy. 

Comments on the proposed text in-line below.

Andrew

On 5/17/2013 9:53 AM, ARIN wrote:
> Draft Policy ARIN-2013-4
> RIR Principles
>
> On 16 May 2013 the ARIN Advisory Council (AC) accepted "ARIN-prop-187
> RIR Principles" as a Draft Policy.
>
> Draft Policy ARIN-2013-4 is below and can be found at:
> https://www.arin.net/policy/proposals/2013_4.html
>
>
> ## * ##
>
>
> Draft Policy ARIN-2013-4
> RIR Principles
>
> Date: 17 May 2013
>
> Problem Statement:
>
> The original text in RFC 2050 both "describes the registry system for
> the distribution of globally unique Internet address space and
> registry operations" and provides "rules and guidelines [principles]
> governing the distribution of this address space."
>
> The currently proposed update (RFC2050bis) "provides information about
> the current Internet Numbers Registry System used in the distribution
> of globally unique Internet Protocol (IP) address space and autonomous
> system (AS) numbers" and "provides information about the processes for
> further evolution of the Internet Numbers Registry System."
>
> This means that the guiding principles of stewardship are not
> currently being carried forward into the new document. The goals of
> Conservation (efficient utilization based on need), Routability
> (hierarchical aggregation), and Registration (uniqueness) are as
> important, if not more so, now that the transition to IPv6 is upon us.
> This can be rectified by documenting these principles in RIR policy.
>
> Policy Statement:
>
> Section 0: Principles and Goals of the Internet Registry System
>
> 0.1. Efficient utilization based on need (Conservation)
>
> Policies for managing Internet number resources must support fair
> distribution of globally unique Internet address space according to
> the operational needs of the end-users and Internet Service Providers
> operating networks using this address space. The registry should
> prevent stockpiling in order to maximize the conservation and
> efficient utilization of the Internet address space.

This section should use the new proposed convention of "LIR/ISP" as
being developed in ARIN-2013-5.

s/this address space/IP number resources/r
s/Internet address space/IP number resources/r

I think this section should have an explicit reference to the difference
in conservation techniques for IPv4 and IPv6.  A proposed sentence might
be something like this... "Conservation goals may vary due to the
technical differences between IP number resources pools, for example the
relatively limited size of the IPv4 address pool causes a desire to see
the number space more highly utilized compared to the vast availability
of IP numbers within the IPv6 address pool."

>
> 0.1.1. Documented Justified Need (Needs Based)
>
> Assignment of Internet number resources is based on documented
> operational need. Utilization rate of address space will be a key
> factor in number resource assignment. To this end, registrants should
> have documented justified need available for each assignment.
> Organizations will be assigned resources based on immediate
> utilization plus expected utilization.

Utilization rate is much more important for IPv4 than IPv6. 

Suggested revision for "Utilization rate of address space will be a key
factor in number resource assignment."

"Utilization rate of address space will be an important factor in
justifying need for IP number resources.  However, utilization rates
will vary due to the technical differences (e.g. IPv4 vs. IPv6) between
number resource pools."

>
> In order to promote increased usage of Internet number resources,
> resource holders will be required to provide an accounting of
> resources currently held demonstrating efficient utilization. Internet
> number resources are valid as long as the criteria continues to be
> met. The transfer of Internet number resources from one party to
> another must be approved by the regional registries. The party trying
> to obtain the resources must meet the same criteria as if they were
> requesting resources directly from the IR.
>
> All Internet number resource requests are subject to audit and
> verification by any means deemed appropriate by the regional registry.
>

I suspect the above two paragraphs may be lightning rods against the
policy proposal.   May I suggest the following single paragraph in lieu 
of the above two paragraphs.

In order meet the Principles and Goals of the Internet Registry System,
resource holders may be required from time to time to provide an
accounting and current usage of resources currently held.  The RIRs
shall set policies to define these accounting mythologies as part of
their community driven policy process.


> 0.2. Hierarchical aggregation (Routability)
>
> Policies for managing Internet number resources must support
> distribution of globally unique Internet addresses in a hierarchical
> manner, permitting the routing scalability of the addresses. This
> scalability is necessary to ensure proper operation of Internet
> routing, although it must be stressed that routability is in no way
> guaranteed with the allocation or assignment of IPv4 addresses.
>

Should the RIR's goals be "LISP agnostic"?  That is if LISP becomes the
predominant routing methodology in the future, one would not necessarily
expect the goals of the RIRs to change. 

Suggested change to end of first sentence.

... permitting the routing scalability of the addresses as required by
the current technical limitations of global routing protocols.

> 0.3. Uniqueness (Registration)
>
> Provision of a public registry documenting Internet number resource
> allocation, reallocation, assignment, and reassignment is necessary to:
>
> a) ensure uniqueness and to to provide operational staff with
> information on who is using the number resource b) to provide a
> contact in case of operational/security problems (e.g. Law
> Enforcement) c) to ensure that a provider has exhausted a majority of
> its current CIDR allocation, thereby justifying an additional
> allocation d) to assist in IP allocation studies.

Suggested revision for "C"

to allow a LIR to demonstrate and disclose reassignment of IP number
resources to third-parties

>
> It is imperative that reassignment information be submitted in a
> prompt and efficient manner to facilitate database maintenance and
> ensure database integrity.
>
> 0.4. Stewardship
>
> It should be noted that efficient utilization and hierarchical
> aggregation are often conflicting goals. All the above goals may
> sometimes be in conflict with the interests of individual end-users or
> Internet Service Providers. Care must be taken to ensure balance with
> these conflicting goals given the resource availability, relative size
> of the resource, and number resource specific technical dynamics, for
> each type of number resource. For example, efficient utilization
> becomes a more prominent issue than aggregation as the IPv4 free pool
> depletes and IPv4 resource availability in any transfer market
> decreases. Conversely, because the IPv6 number space is orders of
> magnitude larger than the IPv4 number space, the scale tips away from
> efficient utilization towards hierarchical aggregation for IPv6 number
> resources.

Perhaps add a statement specifically about Stewardship

"Stewardship of IP number resources is the balance of overseeing and
protecting the interests of all Internet stakeholders to further the
development and expansion of the Internet and the Internet Registry System."

Also...

justified need as a conflicting goal should be explicitly mentioned. 

"It should be noted that efficient utilization, justified need, and
hierarchical aggregation are often conflicting goals."

Use the new LIR/ISP convention instead of "Internet Service Providers"



>
> Comments:
>
> a. Timetable for implementation: immediately
>
> b. I believe that it would be beneficial for IANA to adopt these
> principles as well, and encourage the community to consider a global
> policy proposal.
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.



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

Message: 3
Date: Tue, 28 May 2013 16:09:57 -0400
From: William Herrin <[email protected]>
To: [email protected]
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-4: RIR Principles
Message-ID:
        <CAP-guGUCzdq=n81a9uQ7FCEZEjh_A2dmcgdFbZw8f=_5mf5...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Fri, May 17, 2013 at 12:53 PM, ARIN <[email protected]> wrote:
> 0.2. Hierarchical aggregation (Routability)
>
> Policies for managing Internet number resources must support distribution of
> globally unique Internet addresses in a hierarchical manner, permitting the
> routing scalability of the addresses. This scalability is necessary to
> ensure proper operation of Internet routing, although it must be stressed
> that routability is in no way guaranteed with the allocation or assignment
> of IPv4 addresses.

This puts the cart before the horse. Scalable routing is important and
registry policies must facilitate it. Hierarchical routing is only
important indirectly in service of aggregation which itself serves
scalable routing only because of BGP's technical limitations. Where
BGP is partnered with or superseded by a scalable technology that
doesn't require aggregation, it should not be our policy to preclude
its use.

Suggest rewording as:

0.2. Encourage Scalable Internet Routing

Policies for managing Internet number resources must facilitate
scalable routing. This scalability is necessary to ensure proper
operation of the Internet. In the Border Gateway Protocol, scalability
is achieved by announcing only CIDR aggregates of downstream customer
routes which are as large as possible.

0.2.1 ARIN does not set Internet Routing Policy

While ARIN number policy is informed by current routing technologies
and routing policy choices made by Internet Service Provides, ARIN
does not make policies about how routing must or must not be done.
Allocation or assignment of addresses by ARIN in no way guarantees
that those addresses will be routeable on the public Internet.



Regards,
Bill Herrin


-- 
William D. Herrin ................ [email protected]  [email protected]
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004


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

Message: 4
Date: Tue, 28 May 2013 16:15:26 -0400
From: William Herrin <[email protected]>
To: [email protected]
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-4: RIR Principles
Message-ID:
        <CAP-guGUbX30Tig_4ef=yttzjwjoe5pgmfgr+hpecvml1c9q...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

On Fri, May 17, 2013 at 12:53 PM, ARIN <[email protected]> wrote:
> 0.1. Efficient utilization based on need (Conservation)
>
> Policies for managing Internet number resources must support fair
> distribution of globally unique Internet address space according to the
> operational needs of the end-users and Internet Service Providers operating
> networks using this address space. The registry should prevent stockpiling
> in order to maximize the conservation and efficient utilization of the
> Internet address space.

This is backwards. Conservation is not the goal. SUSTAINABILITY is the
goal. Depending on the circumstance, conservation may or may not
facilitate sustainability.

Regards,
Bill Herrin


-- 
William D. Herrin ................ [email protected]  [email protected]
3005 Crane Dr. ...................... Web: <http://bill.herrin.us/>
Falls Church, VA 22042-3004


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

Message: 5
Date: Wed, 29 May 2013 00:04:34 -0400
From: Jason Schiller <[email protected]>
To: [email protected]
Cc: "[email protected]" <[email protected]>
Subject: Re: [arin-ppml] Draft Policy ARIN-2013-4: RIR Principles
Message-ID:
        <cac4yj2x5remo1rmq35q-lwbari4vim41y4ouewav6bhanq6...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Andrew thanks for your feed back.

I want to point out that much of this language comes from either RFC-2050
or the current PDP or NRPM.  I tired to change the language as little as
possible, except where we have commonly agreed on new language such as
"efficient utilization" instead of conservation.  I thought that might be
the most uncontroversial starting point.  I am not opposed to changing it,
especially if it makes the text less controversial.

---

WRT the LIR/ISP I agree, we should adopt whatever we think the standard
term should be.

---

WRT using number resources instead of IP address space I would have to take
a careful look and make sure we are not applying principles that make sense
with respect IP addressing to ASNs if they don't make sense.   It is not
clear to me if you think these changes should be throughout the text, or
only in section 0.1.

---

Andrew writes:
> I think this section [0.1. Efficient utilization based on need
(Conservation)]
> should have an explicit reference to the difference
> in conservation techniques for IPv4 and IPv6.  A proposed sentence might
> be something like this... "Conservation goals may vary due to the
> technical differences between IP number resources pools, for example the
> relatively limited size of the IPv4 address pool causes a desire to see
> the number space more highly utilized compared to the vast availability
> of IP numbers within the IPv6 address pool."

I made a conscious effort to keep this text in section 0.4 for clarity.

>From the draf policy section 0.4:
"For example, efficient utilization becomes a more prominent issue than
aggregation as the IPv4 free pool depletes and IPv4 resource availability
in any transfer market decreases. Conversely, because the IPv6 number space
is orders of magnitude larger than the IPv4 number space, the scale tips
away from efficient utilization towards hierarchical aggregation for IPv6
number resources."

Does that text fulfill your suggestion of "Conservation goals may vary due
to the technical differences between IP number resources pools, for example
the relatively limited size of the IPv4 address pool causes a desire to see
the number space more highly utilized compared to the vast availability of
IP numbers within the IPv6 address pool."

Do you have concerns about where this text is located?

---

Andrew writes:
> "Utilization rate of address space will be an important factor in
> justifying need for IP number resources.  However, utilization rates
> will vary due to the technical differences (e.g. IPv4 vs. IPv6) between
> number resource pools."

Again, I made a conscious effort to keep this text in section 0.4 for
clarity, and would quote the same text.

Does that meet your concern about your proposed text?

Do you have concerns about where this text is located?

Should I repeat the paragraph in 0.1, 0.1.1, and 0.4?

---
Andrew writes:
>> In order to promote increased usage of Internet number resources,
>> resource holders will be required to provide an accounting of
>> resources currently held demonstrating efficient utilization. Internet
>> number resources are valid as long as the criteria continues to be
>> met. The transfer of Internet number resources from one party to
>> another must be approved by the regional registries. The party trying
>> to obtain the resources must meet the same criteria as if they were
>> requesting resources directly from the IR.
>>
>> All Internet number resource requests are subject to audit and
>> verification by any means deemed appropriate by the regional registry.
>>
>
> I suspect the above two paragraphs may be lightning rods against the
> policy proposal.   May I suggest the following single paragraph in lieu
> of the above two paragraphs.
>
> In order meet the Principles and Goals of the Internet Registry System,
> resource holders may be required from time to time to provide an
> accounting and current usage of resources currently held.  The RIRs
> shall set policies to define these accounting mythologies as part of
> their community driven policy process.

I'm not sure why you think these two paragraphs are lightening rods.

RFC-250 3.3 says:
"To promote increased usage of address space, the registries will
  require an accounting of address space previously assigned to the
  enterprise, if any."

RFC-2050 3.1 says:

"IP addresses are valid as long as the criteria continues to be met."

RFC-2050 4.7 says

"The transfer of IP addresses from one party to another must be
  approved by the regional registries.  The party trying to obtain
  the IP address must meet the same criteria as if they were
  requesting an IP address directly from the IR."

RFC-2050 4.4 says:
"All IP address requests are subject to audit and verification
  by any means deemed appropriate by the regional registry."

And there is lots of text about conservation in RFC-2050 and
efficient utilization in the NRPM.

Can you elaborate on the lightening rod potin?

I can only guess you are suggesting that the community wants
to depart from the principles in RFC-2050, but think you must
mean something else.

What am I missing here?

---

Andrew writes:
>> 0.2. Hierarchical aggregation (Routability)
>>
>> Policies for managing Internet number resources must support
>> distribution of globally unique Internet addresses in a hierarchical
>> manner, permitting the routing scalability of the addresses.
>
> Should the RIR's goals be "LISP agnostic"?  That is if LISP becomes the
> predominant routing methodology in the future, one would not necessarily
> expect the goals of the RIRs to change.
>
> Suggested change to end of first sentence.
>
> ... permitting the routing scalability of the addresses as required by
> the current technical limitations of global routing protocols.

I think this change is good even w/o considering LISP.
Imagine we have new holographic memory that can hold orders of
magnitude more data and decrease read time

---

Andrew writes:
>
>> 0.3. Uniqueness (Registration)
>>
>> c) to ensure that a provider has exhausted a majority of
>> its current CIDR allocation, thereby justifying an additional
>> allocation d) to assist in IP allocation studies.
>
> Suggested revision for "C"
>
> to allow a LIR to demonstrate and disclose reassignment of IP number
> resources to third-parties

I think the point is to demonstrate reassignment data to
demonstrate efficient utilization.
But I also think that point is covered in section 0.1.1, So the rewrite
here is ok.

---

Andrew writes:
> Perhaps add a statement specifically about Stewardship
>
> "Stewardship of IP number resources is the balance of overseeing and
> protecting the interests of all Internet stakeholders to further the
> development and expansion of the Internet and the Internet Registry
System."

I do not oppose this text.

Andrew also writes...
>
> justified need as a conflicting goal should be explicitly mentioned.
>
> "It should be noted that efficient utilization, justified need, and
>hierarchical aggregation are often conflicting goals."

I'm not sure this parses correctly...  This sounds to me like there are
conflicts between all three:

efficient utilization vs justified need vs hierarchical aggregation.

How about:
"It should be noted that efficient utilization based on justified need, and
hierarchical aggregation are often conflicting goals."



-


On Tue, May 28, 2013 at 2:19 PM, Andrew Dul <[email protected]> wrote:

> I support adding these guiding principles to the NRPM, furthermore I
> would support efforts to introduce this policy in all RIR regions to
> make this a global policy.
>
> Comments on the proposed text in-line below.
>
> Andrew
>
> On 5/17/2013 9:53 AM, ARIN wrote:
> > Draft Policy ARIN-2013-4
> > RIR Principles
> >
> > On 16 May 2013 the ARIN Advisory Council (AC) accepted "ARIN-prop-187
> > RIR Principles" as a Draft Policy.
> >
> > Draft Policy ARIN-2013-4 is below and can be found at:
> > https://www.arin.net/policy/proposals/2013_4.html
> >
> >
> > ## * ##
> >
> >
> > Draft Policy ARIN-2013-4
> > RIR Principles
> >
> > Date: 17 May 2013
> >
> > Problem Statement:
> >
> > The original text in RFC 2050 both "describes the registry system for
> > the distribution of globally unique Internet address space and
> > registry operations" and provides "rules and guidelines [principles]
> > governing the distribution of this address space."
> >
> > The currently proposed update (RFC2050bis) "provides information about
> > the current Internet Numbers Registry System used in the distribution
> > of globally unique Internet Protocol (IP) address space and autonomous
> > system (AS) numbers" and "provides information about the processes for
> > further evolution of the Internet Numbers Registry System."
> >
> > This means that the guiding principles of stewardship are not
> > currently being carried forward into the new document. The goals of
> > Conservation (efficient utilization based on need), Routability
> > (hierarchical aggregation), and Registration (uniqueness) are as
> > important, if not more so, now that the transition to IPv6 is upon us.
> > This can be rectified by documenting these principles in RIR policy.
> >
> > Policy Statement:
> >
> > Section 0: Principles and Goals of the Internet Registry System
> >
> > 0.1. Efficient utilization based on need (Conservation)
> >
> > Policies for managing Internet number resources must support fair
> > distribution of globally unique Internet address space according to
> > the operational needs of the end-users and Internet Service Providers
> > operating networks using this address space. The registry should
> > prevent stockpiling in order to maximize the conservation and
> > efficient utilization of the Internet address space.
>
> This section should use the new proposed convention of "LIR/ISP" as
> being developed in ARIN-2013-5.
>
> s/this address space/IP number resources/r
> s/Internet address space/IP number resources/r
>
> I think this section should have an explicit reference to the difference
> in conservation techniques for IPv4 and IPv6.  A proposed sentence might
> be something like this... "Conservation goals may vary due to the
> technical differences between IP number resources pools, for example the
> relatively limited size of the IPv4 address pool causes a desire to see
> the number space more highly utilized compared to the vast availability
> of IP numbers within the IPv6 address pool."
>
> >
> > 0.1.1. Documented Justified Need (Needs Based)
> >
> > Assignment of Internet number resources is based on documented
> > operational need. Utilization rate of address space will be a key
> > factor in number resource assignment. To this end, registrants should
> > have documented justified need available for each assignment.
> > Organizations will be assigned resources based on immediate
> > utilization plus expected utilization.
>
> Utilization rate is much more important for IPv4 than IPv6.
>
> Suggested revision for "Utilization rate of address space will be a key
> factor in number resource assignment."
>
> "Utilization rate of address space will be an important factor in
> justifying need for IP number resources.  However, utilization rates
> will vary due to the technical differences (e.g. IPv4 vs. IPv6) between
> number resource pools."
>
> >
> > In order to promote increased usage of Internet number resources,
> > resource holders will be required to provide an accounting of
> > resources currently held demonstrating efficient utilization. Internet
> > number resources are valid as long as the criteria continues to be
> > met. The transfer of Internet number resources from one party to
> > another must be approved by the regional registries. The party trying
> > to obtain the resources must meet the same criteria as if they were
> > requesting resources directly from the IR.
> >
> > All Internet number resource requests are subject to audit and
> > verification by any means deemed appropriate by the regional registry.
> >
>
> I suspect the above two paragraphs may be lightning rods against the
> policy proposal.   May I suggest the following single paragraph in lieu
> of the above two paragraphs.
>
> In order meet the Principles and Goals of the Internet Registry System,
> resource holders may be required from time to time to provide an
> accounting and current usage of resources currently held.  The RIRs
> shall set policies to define these accounting mythologies as part of
> their community driven policy process.
>
>
> > 0.2. Hierarchical aggregation (Routability)
> >
> > Policies for managing Internet number resources must support
> > distribution of globally unique Internet addresses in a hierarchical
> > manner, permitting the routing scalability of the addresses. This
> > scalability is necessary to ensure proper operation of Internet
> > routing, although it must be stressed that routability is in no way
> > guaranteed with the allocation or assignment of IPv4 addresses.
> >
>
> Should the RIR's goals be "LISP agnostic"?  That is if LISP becomes the
> predominant routing methodology in the future, one would not necessarily
> expect the goals of the RIRs to change.
>
> Suggested change to end of first sentence.
>
> ... permitting the routing scalability of the addresses as required by
> the current technical limitations of global routing protocols.
>
> > 0.3. Uniqueness (Registration)
> >
> > Provision of a public registry documenting Internet number resource
> > allocation, reallocation, assignment, and reassignment is necessary to:
> >
> > a) ensure uniqueness and to to provide operational staff with
> > information on who is using the number resource b) to provide a
> > contact in case of operational/security problems (e.g. Law
> > Enforcement) c) to ensure that a provider has exhausted a majority of
> > its current CIDR allocation, thereby justifying an additional
> > allocation d) to assist in IP allocation studies.
>
> Suggested revision for "C"
>
> to allow a LIR to demonstrate and disclose reassignment of IP number
> resources to third-parties
>
> >
> > It is imperative that reassignment information be submitted in a
> > prompt and efficient manner to facilitate database maintenance and
> > ensure database integrity.
> >
> > 0.4. Stewardship
> >
> > It should be noted that efficient utilization and hierarchical
> > aggregation are often conflicting goals. All the above goals may
> > sometimes be in conflict with the interests of individual end-users or
> > Internet Service Providers. Care must be taken to ensure balance with
> > these conflicting goals given the resource availability, relative size
> > of the resource, and number resource specific technical dynamics, for
> > each type of number resource. For example, efficient utilization
> > becomes a more prominent issue than aggregation as the IPv4 free pool
> > depletes and IPv4 resource availability in any transfer market
> > decreases. Conversely, because the IPv6 number space is orders of
> > magnitude larger than the IPv4 number space, the scale tips away from
> > efficient utilization towards hierarchical aggregation for IPv6 number
> > resources.
>
> Perhaps add a statement specifically about Stewardship
>
> "Stewardship of IP number resources is the balance of overseeing and
> protecting the interests of all Internet stakeholders to further the
> development and expansion of the Internet and the Internet Registry
> System."
>
> Also...
>
> justified need as a conflicting goal should be explicitly mentioned.
>
> "It should be noted that efficient utilization, justified need, and
> hierarchical aggregation are often conflicting goals."
>
> Use the new LIR/ISP convention instead of "Internet Service Providers"
>
>
>
> >
> > Comments:
> >
> > a. Timetable for implementation: immediately
> >
> > b. I believe that it would be beneficial for IANA to adopt these
> > principles as well, and encourage the community to consider a global
> > policy proposal.
> > _______________________________________________
> > PPML
> > You are receiving this message because you are subscribed to
> > the ARIN Public Policy Mailing List ([email protected]).
> > Unsubscribe or manage your mailing list subscription at:
> > http://lists.arin.net/mailman/listinfo/arin-ppml
> > Please contact [email protected] if you experience any issues.
>
> _______________________________________________
> PPML
> You are receiving this message because you are subscribed to
> the ARIN Public Policy Mailing List ([email protected]).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact [email protected] if you experience any issues.
>



-- 
_______________________________________________________
Jason Schiller|NetOps|[email protected]|571-266-0006
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.arin.net/pipermail/arin-ppml/attachments/20130529/ff1ab44f/attachment.html>

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

_______________________________________________
ARIN-PPML mailing list
[email protected]
http://lists.arin.net/mailman/listinfo/arin-ppml

End of ARIN-PPML Digest, Vol 95, Issue 12
*****************************************

Reply via email to