That address is no longer active, you need to register with the portal now: https://portal.ampr.org

More details to follow

Regards, Chris - G1FEF

On 25 Jan 2013, at 19:49, Paul wrote:

(Please trim inclusions from previous messages) _______________________________________________

gateways@ampr.org

Paul Delaney - K6HR http://k6hr.dyndns.org:8080

-----Original Message----- From: 44net-bounces+paul.hamradio=verizon.net@hamradio.ucsd.edu [mailto:44net-bounces+paul.hamradio=verizon.net@hamradio.ucsd.edu] On Behalf Of K7ILO Sent: Friday, January 25, 2013 11:31 AM To: 44net@hamradio.ucsd.edu Subject: [44net] ip updating

(Please trim inclusions from previous messages) _______________________________________________ Hello gang.

Could an ip coordinator send me via direct email the email robot's address for adding and updating amprnet ip addresses?

Thanks

Harold K7ilo (formerly KB7RSI) Southern Nevada Ip Coordinator

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

On 25 Jan 2013, at 20:19, Bill Vodall wrote:

(Please trim inclusions from previous messages) _______________________________________________

...

Now is probably a good time to ask everyone that is currently using an IP or IPs from the 44/8 to register on the portal:

https://portal.ampr.org

Would it be possible to have some simple text search on the database? For example, just where is "WA7NWP" mentioned these days...

Bill, WA7NWP

I will add it to my TODO list, which seems to grow longer every day, so no promises when it might get done ;-)

Chris

If it can't be found, I have a printed copy that I can scan as a .pdf file and provide.

Hey Jack. Long time.

Harold K7ILO (formerly KB7RSI) On Jan 31, 2013 11:05 AM, "Jack Eifer" jeifer@cwo.com wrote:

(Please trim inclusions from previous messages) _______________________________________________ Chris,

While we're on the subject of TODO's, Has any consideration or thought been given to resurrecting the 'GATEWAY' file that Fuller maintained ?

I found the information in file useful and easy to access. Perhaps the new website has the same info embedded, but somewhere I've yet to discover.

Jack, AA6HF

On Jan 31, 2013, at 8:17 AM, Chris Smith chris@g1fef.co.uk wrote:

...

(Please trim inclusions from previous messages) _______________________________________________ On 25 Jan 2013, at 20:19, Bill Vodall wrote:

...

(Please trim inclusions from previous messages) _______________________________________________

...

Now is probably a good time to ask everyone that is currently using an

IP or IPs from the 44/8 to register on the portal:

...

...

...

https://portal.ampr.org

Would it be possible to have some simple text search on the database? For example, just where is "WA7NWP" mentioned these days...

Bill, WA7NWP

I will add it to my TODO list, which seems to grow longer every day, so

no promises when it might get done ;-)

...

Chris

---

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

On 31 Jan 2013, at 19:05, Jack Eifer wrote:

(Please trim inclusions from previous messages) _______________________________________________ Chris,

While we're on the subject of TODO's, Has any consideration or thought been given to resurrecting the 'GATEWAY' file that Fuller maintained ?

Yes, this is on my TODO list as it has been requested by someone else.

Although the old data from Jim's system is available, it was quite out of date, so the new gateways file will be populated from the current data in the portal database, but the format will be the same.

Should be available fairly soon.

Chris

Hi David,

A couple of issues that I see coming down the line as a regional coordinator.

1. Persons receiving an allocation disappear after a period of time, abandoning the allocation in the process, and don't release the allocation. There is no apparent method for the regional coordinator to attempt contact with the person and or release the allocation if the person cannot be contacted or found.

This is already addressed in the new system: After a suitable period of time following the initial allocation, the system will email the end user of the allocated subnet with a link asking them to click on the link to confirm they are still active and using the IP's. For anyone not wishing to click on a link in an email, the email will also advise them that they can login to the portal as usual to confirm their ongoing use of the subnet.

If there is no response, a second email is sent a while later, this time an email is also sent to the co-ordinator, so they are aware that the first contact attempt timed out. The co-ordinator may be able to assist at this point by giving the person a "nudge".

If the second email gets no response, a third email is sent to both end user and co-ordinator, advising that the allocated subnet has been de-activated, but that it can be re-activated if they respond to the email.

At this point the subnet is removed from any gateways and DNS, but remains in the database as a de-activated entry.

After a suitable period of time a final email is sent to user and co-ordinator advising them that the subnet has been deleted and returned to the pool.

Regards, Chris

Hi Bob,

This seems reasonable for recovering allocations, but how do you deal with coordinators that go silent and stop processing requests for their area?

The same process occurs, the regional co-ordinators and above them, the country co-ordinators are seen by the system as "responsible" for the subnet allocated to them. If a regional or country co-ordinator fails to respond and there are allocated addresses within their subnet obviously the subnet is not de-activated or deleted, however the responsibility does pass to the next level up.

If a regional co-ordinator failed to respond the subnet defaults back to the country co-ordinator, who can then attempt to find someone else to look after the region.

Ultimately, if a country co-ordinator fails to respond, the country's subnet would default back to Brian, who then has to try and find a new country co-ordinator.

Are regional coordinators really necessary, can't the blocks be managed centrally with an automated system, as long as the block being requested are within some specific guidelines?

Countries vary in their setup, some just have one person that looks after the entire subnet, others, e.g. the US have regional co-ordinators to spread the workload, some have specific rules for allocating IP's, and so on. All the portal is trying to do is maintain an up to date list of what IP's are being used and who is responsible for them, how they are allocated is up to the country's co-ordinator, who are we to dictate how a country is to allocate their IP's?

Regards, Chris

Bob

From: Chris Smith chris@g1fef.co.uk To: w7szs@noapra.org; AMPRNet working group 44net@hamradio.ucsd.edu Sent: Friday, February 1, 2013 4:38:42 AM Subject: Re: [44net] Coordinator Privileges on Amprnet Portal

(Please trim inclusions from previous messages) _______________________________________________ Hi David,

...

A couple of issues that I see coming down the line as a regional coordinator.

1. Persons receiving an allocation disappear after a period of time, abandoning the allocation in the process, and don't release the allocation. There is no apparent method for the regional coordinator to attempt contact with the person and or release the allocation if the person cannot be contacted or found.

This is already addressed in the new system: After a suitable period of time following the initial allocation, the system will email the end user of the allocated subnet with a link asking them to click on the link to confirm they are still active and using the IP's. For anyone not wishing to click on a link in an email, the email will also advise them that they can login to the portal as usual to confirm their ongoing use of the subnet.

If there is no response, a second email is sent a while later, this time an email is also sent to the co-ordinator, so they are aware that the first contact attempt timed out. The co-ordinator may be able to assist at this point by giving the person a "nudge".

If the second email gets no response, a third email is sent to both end user and co-ordinator, advising that the allocated subnet has been de-activated, but that it can be re-activated if they respond to the email.

At this point the subnet is removed from any gateways and DNS, but remains in the database as a de-activated entry.

After a suitable period of time a final email is sent to user and co-ordinator advising them that the subnet has been deleted and returned to the pool.

Regards, Chris

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

On Fri, 1 Feb 2013, Chris Smith wrote:

Date: Fri, 1 Feb 2013 09:38:42 +0000 From: Chris Smith chris@g1fef.co.uk Reply-To: AMPRNet working group 44net@hamradio.ucsd.edu To: w7szs@noapra.org, AMPRNet working group 44net@hamradio.ucsd.edu Subject: Re: [44net] Coordinator Privileges on Amprnet Portal

(Please trim inclusions from previous messages) _______________________________________________ Hi David,

...

A couple of issues that I see coming down the line as a regional coordinator.

1. Persons receiving an allocation disappear after a period of time,

abandoning the allocation in the process, and don't release the allocation. There is no apparent method for the regional coordinator to attempt contact with the person and or release the allocation if the person cannot be contacted or found.

This is already addressed in the new system: After a suitable period of time following the initial allocation, the system will email the end user of the allocated subnet with a link asking them to click on the link to confirm they are still active and using the IP's. For anyone not wishing to click on a link in an email, the email will also advise them that they can login to the portal as usual to confirm their ongoing use of the subnet.

I recommend adding a link from the portal to the TOS which spells out the allocation period and terms.

http://www.ampr.org/tos.txt

BTW, any reason why ampr.org and www.ampr.org can't have exactly the same IP address (or make one a cname) so that entering either one gets you to the same website? Ie. the 'www' shouldn't really be necessary in a URI. The 44.0.0.1 address is already nailed down by gw.

Antonio Querubin e-mail: tony@lavanauts.org xmpp: antonioquerubin@gmail.com

Chris, your description on the automated renewal and recovery process of allocations is clear and reasonable. The remaining question I have is what is the current time value definition for a "suitable period of time"?

David, W7SZS

On 02/01/2013 01:38 AM, Chris Smith wrote:

Hi David,

...

A couple of issues that I see coming down the line as a regional coordinator.

1. Persons receiving an allocation disappear after a period of time, abandoning the allocation in the process, and don't release the allocation. There is no apparent method for the regional coordinator to attempt contact with the person and or release the allocation if the person cannot be contacted or found.

This is already addressed in the new system: After a suitable period of time following the initial allocation, the system will email the end user of the allocated subnet with a link asking them to click on the link to confirm they are still active and using the IP's. For anyone not wishing to click on a link in an email, the email will also advise them that they can login to the portal as usual to confirm their ongoing use of the subnet.

If there is no response, a second email is sent a while later, this time an email is also sent to the co-ordinator, so they are aware that the first contact attempt timed out. The co-ordinator may be able to assist at this point by giving the person a "nudge".

If the second email gets no response, a third email is sent to both end user and co-ordinator, advising that the allocated subnet has been de-activated, but that it can be re-activated if they respond to the email.

At this point the subnet is removed from any gateways and DNS, but remains in the database as a de-activated entry.

After a suitable period of time a final email is sent to user and co-ordinator advising them that the subnet has been deleted and returned to the pool.

Regards, Chris

If a subnet is laying dormant in your coverage area (and there are many) it is up for grabs for you to route. But you have to make absolutely sure that no one is planing to route that subnet already. You are only doing people who are already having an address/host name in it a favour. The first thing you should do if you start a gateway is to look for old subnets in your coverage area who are laying dormant in my opinion.

Bob VE3TOK

On 13-02-01 12:28 AM, David Warner wrote:

(Please trim inclusions from previous messages) _______________________________________________ A couple of issues that I see coming down the line as a regional coordinator.

1. Persons receiving an allocation disappear after a period of time,

abandoning the allocation in the process, and don't release the allocation. There is no apparent method for the regional coordinator to attempt contact with the person and or release the allocation if the person cannot be contacted or found.

2. Since a person has to register on the Amprnet portal and provide

contact information, it would seem logical for the coordinator to be able to see the contact record.

3. In lieu of providing the regional coordinator a method to recover

abandoned allocations, put an expiration date on the allocation with notification to the person receiving the allocation that they must log into the portal to renew the allocation prior to expiration. The expiration date would relative to the date of issuance or renewal. I would say a 2 to 5 year reservation on the allocation seems reasonable.

David, W7SZS _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

This seems to me why blocks should be announced (probably via bgp).

AF6EP

On Fri, Feb 1, 2013 at 1:43 PM, Bob Scanferla va3rjs@yahoo.ca wrote:

(Please trim inclusions from previous messages) _______________________________________________

That is fine but how do you make sure no one is planning to route it and how would a dispute be resolved...this is much like repeater pairs and why they are usually coordinated in an area.

I may give it a try and see where it goes, I will just squat on a block and see who screams :)

Thanks Bob _______________________________________________ If a subnet is laying dormant in your coverage area (and there are many) it is up for grabs for you to route. But you have to make absolutely sure that no one is planing to route that subnet already. You are only doing people who are already having an address/host name in it a favour. The first thing you should do if you start a gateway is to look for old subnets in your coverage area who are laying dormant in my opinion.

Bob VE3TOK

On 13-02-01 12:28 AM, David Warner wrote:

(Please trim inclusions from previous messages) _______________________________________________ A couple of issues that I see coming down the line as a regional coordinator.

1. Persons receiving an allocation disappear after a period of time,

abandoning the allocation in the process, and don't release the allocation. There is no apparent method for the regional coordinator to attempt contact with the person and or release the allocation if the person cannot be contacted or found.

2. Since a person has to register on the Amprnet portal and provide

contact information, it would seem logical for the coordinator to be able to see the contact record.

3. In lieu of providing the regional coordinator a method to recover

abandoned allocations, put an expiration date on the allocation with notification to the person receiving the allocation that they must log into the portal to renew the allocation prior to expiration. The expiration date would relative to the date of issuance or renewal. I would say a 2 to 5 year reservation on the allocation seems reasonable.

David, W7SZS _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

On Fri, Feb 1, 2013 at 2:15 PM, Brian Kantor Brian@ucsd.edu wrote:

(Please trim inclusions from previous messages) _______________________________________________ On Fri, Feb 01, 2013 at 01:49:17PM -0800, Eric Fort wrote:

...

This seems to me why blocks should be announced (probably via bgp).

BGP-routed subnets *are* announced via BGP. Tunnel-routed subnets are announced via RIP and the manual gateway/encap file. - Brian

Wasn't saying they were not announced, merely that those in use should be (larger blocks via bgp, small subnets via RIP) and if they are probably should not be stepped on or used without coordination with the party primarily allocated that block/subnet. one or more SWIP servers with a requirement that all who are allocated address space keep their contact info current would likely be quite useful here.

AF6EP