[address-policy-wg] 2014-03 Policy Proposal Withdrawn (Remove Multihoming Requirement for AS Number Assignments)

I agree. Perhaps the use cases were too narrow? I see (and practice) single homing on a wide scale and the efficiencies of doing it responsibly are valuable to big and small alike IMHO. I don't recall the proposal and didn't pay attention to it. Mea culpa.

Best,

-M<



________________________________________
From: David Huberman <David.Huberman at microsoft.com>
Sent: Monday, November 9, 2015 11:57 AM
To: address-policy-wg at ripe.net
Subject: Re: [address-policy-wg] 2014-03 Policy Proposal Withdrawn      (Remove Multihoming Requirement for AS Number Assignments)

As a community, I think it is important we resurrect this proposal as soon as possible.  Requiring classic multi homing in order to obtain an AS Number is out of step with current engineering and operational practices.

Can the authors, the chairs, the staff, or any knowledgeable observer please outline where the impasse is?

I'd like to help get this back on the docket, but need to understand the bottom line.

Thank you
David

David R Huberman
Microsoft Corporation
Principal, Global IP Addressing

________________________________________
From: address-policy-wg <address-policy-wg-bounces at ripe.net> on behalf of Marco Schmidt <mschmidt at ripe.net>
Sent: Monday, November 9, 2015 7:20:02 AM
To: address-policy-wg at ripe.net
Subject: [address-policy-wg] 2014-03 Policy Proposal Withdrawn (Remove  Multihoming Requirement for AS Number Assignments)

Dear colleagues,


The proposal 2014-03, "Remove Multihoming Requirement for AS Number Assignments" has been withdrawn.

It is now archived and can be found at:

    https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.ripe.net%2fparticipate%2fpolicies%2farchived-policy-proposals%2farchive-policy-proposals%2f&data=01%7c01%7cDAVID.HUBERMAN%40microsoft.com%7c06032ab2d4b940bc9e9108d2e919567e%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=viQADY8DeLG%2fIyaMw6R62%2bJ5%2fVarFDLm4DFipQQcCT8%3d


Reason for withdrawal:

    The proposers decided to withdraw the proposal due to the inability to find an acceptable solution which satisfied all parties.


Regards,

Marco Schmidt
Policy Development Officer
RIPE NCC