Is this transitive? I.E. Org A gets a 4.1.8.2. Org B acquires Org A
and under 8.2 keeps the 4.1.8.2 resources. Does the restriction that
they can only be transferred to Org C via 8.2 still apply? (I think it
should, but IANAL, and I think this needs to be worded carefully to
avoid opening
So wrong. You aren't including size.
2019.
On Tue, May 21, 2019 at 18:01 Aaron Dudek wrote:
> Don't we need to have a policy to decide which font family we want the
> italics to come from?
>
> On Tue, May 21, 2019 at 5:25 PM Michael Williams
> wrote:
> >
> > +1. We need a draft policy on use
On Tue, May 21, 2019 at 12:52:16PM -0700, Seth Mattinen wrote:
> On 5/21/19 11:02 AM, ARIN wrote:
> > Draft Policy ARIN-2019-13: ARIN Membership Legal Jurisdiction Exclusion
>
> Oppose this one too.
>
> What's with the burst of "how to be excluded from ARIN jurisdiction"
> proposals right after
Hi Albert,
> Albert Erdmann wrote :
> The impact of squatting, as long as the routes do not leak outside
> are 100% on the networks that are doing the squatting.
Agreed. I also agree that ARIN should not do anything do enforce it (even
stronger case as prop-266). And I also agree that it should
As the draft is written, I would assume it applies to all blocks issued
under 4.1.8.2 because the draft policy doesn't state otherwise. We
certainly could craft the policy to only apply going forward or it could
also be applicable to all wait-list blocks.
If members of the community have a
+1. We need a draft policy on use of italics in plaintext emails. I’ll
coauthor with anyone’s who’s interested.
Sent from my iPhone
> Adam Thompson wrote:
>
> I admit I'm being mildly pedantic, but... italics? In a plain-text email?
>
> Adam Thompson
> Consultant, Infrastructure Services
>
I admit I'm being mildly pedantic, but... italics? In a plain-text email?
Adam Thompson
Consultant, Infrastructure Services
MERLIN
100 - 135 Innovation Drive
Winnipeg, MB, R3T 6A8
(204) 977-6824 or 1-800-430-6404 (MB only)
athomp...@merlin.mb.ca
www.merlin.mb.ca
> -Original Message-
>
A suggestion would be to put this in its own subsection and reuse the text in
4.2.3.8, removing the 36 months and adding allocation/assignment. Reuse of
language is helpful as the language has already been vetted.
4.1.8.3 IP allocations or assignments issued through 4.1.8 are non-transferable
On Tue, May 21, 2019 at 11:06 AM ARIN wrote:
> Draft Policy ARIN-2019-14: No Specified Transfers for 4.1.8.2 Blocks
>
> Policy Statement:
>
> Add a second paragraph to 4.1.8.2:
>
> IP allocations issued through 4.1.8.2 are non-transferable via section
> 8.3 and section 8.4. In the case of a
On 5/21/19 11:06 AM, ARIN wrote:
Policy Statement:
Add a second paragraph to 4.1.8.2:
IP allocations issued through 4.1.8.2 are non-transferable via section
8.3 and section 8.4. In the case of a section 8.2, transfer of the IP
assignment must be utilized for the same purpose or needs
On 5/21/19 11:02 AM, ARIN wrote:
Draft Policy ARIN-2019-13: ARIN Membership Legal Jurisdiction Exclusion
Oppose this one too.
What's with the burst of "how to be excluded from ARIN jurisdiction"
proposals right after the successful fraud case? Are the fraudsters
suddenly concerned?
~Seth
On 5/21/19 11:01 AM, ARIN wrote:
Draft Policy ARIN-2019-11: M Regional Nexus Exclusion
Oppose.
~Seth
___
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
Unsubscribe or
On 5/21/19 11:02 AM, ARIN wrote:
Draft Policy ARIN-2019-12: M Legal Jurisdiction Exclusion
Also oppose.
~Seth
___
ARIN-PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List (ARIN-PPML@arin.net).
On Tue, May 21, 2019 at 1:03 PM ARIN wrote:
Policy statement seems to fail to propose a substantive change to
the NRPM.
Section 9 is already much more detailed, and there's nothing there
stating entities must be incorporated within ARIN service region;
although they must be carrying out
On 16 May 2019, the ARIN Advisory Council (AC) accepted "ARIN-prop-274:
No Specified Transfers for 4.1.8.2 Blocks" as a Draft Policy.
Draft Policy ARIN-2019-14 is below and can be found at:
https://www.arin.net/participate/policy/drafts/2019_14/
You are encouraged to discuss all Draft Policies
On 16 May 2019, the ARIN Advisory Council (AC) accepted "ARIN-prop-273:
ARIN Membership Legal Jurisdiction Exclusion" as a Draft Policy.
Draft Policy ARIN-2019-13 is below and can be found at:
https://www.arin.net/participate/policy/drafts/2019_13/
You are encouraged to discuss all Draft
On 16 May 2019, the ARIN Advisory Council (AC) accepted "ARIN-prop-272:
M Legal Jurisdiction Exclusion" as a Draft Policy.
Draft Policy ARIN-2019-12 is below and can be found at:
https://www.arin.net/participate/policy/drafts/2019_12/
You are encouraged to discuss all Draft Policies on PPML.
On 16 May 2019, the ARIN Advisory Council (AC) accepted "ARIN-prop-271:
M Regional Nexus Exclusion" as a Draft Policy.
Draft Policy ARIN-2019-11 is below and can be found at:
https://www.arin.net/participate/policy/drafts/2019_11/
You are encouraged to discuss all Draft Policies on PPML. The
On 16 May 2019, the ARIN Advisory Council (AC) accepted "ARIN-prop-270:
Inter-RIR M" as a Draft Policy.
Draft Policy ARIN-2019-10 is below and can be found at:
https://www.arin.net/participate/policy/drafts/2019_10/
You are encouraged to discuss all Draft Policies on PPML. The AC will
On 16 May 2019, the ARIN Advisory Council (AC) accepted "ARIN-prop-269:
Clarify Interactions Between NRPM 4.10 IPv6 Transition Space Requests
and NRPM 4.1.8.2 Unmet Needs Requests" as a Draft Policy.
Draft Policy ARIN-2019-9 is below and can be found at:
On 16 May 2019, the ARIN Advisory Council (AC) accepted "ARIN-prop-268:
Clarification of Section 4.10 for Multiple Discrete Networks" as a Draft
Policy.
Draft Policy ARIN-2019-8 is below and can be found at:
https://www.arin.net/participate/policy/drafts/2019_8/
You are encouraged to discuss
In accordance with the Policy Development Process (PDP), the Advisory
Council met on 16 May 2019.
The AC has advanced the following to the Board of Trustees for review:
* ARIN-2017-12: POC Notification and Validation Upon Reassignment or
Reallocation
* ARIN-2018-2: Clarification to ISP
22 matches
Mail list logo
